clock: Avoid creating a weakref with every entry
Creating and destroying weakrefs takes a write lock on a global
GRWLock
. This makes for a very contended lock when the pipeline has
many synchronizing elements.
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Creating and destroying weakrefs takes a write lock on a global
GRWLock
. This makes for a very contended lock when the pipeline has
many synchronizing elements.