summary refs log tree commit diff
path: root/synapse/events/builder.py
diff options
context:
space:
mode:
authorRichard van der Hoff <richard@matrix.org>2018-10-22 16:12:11 +0100
committerRichard van der Hoff <richard@matrix.org>2018-10-22 16:12:11 +0100
commitc7273c11bc73630e3f2ab1a82d20a40d8b17f9a3 (patch)
tree659a03763a1c6492399f2f34d625d482961c0126 /synapse/events/builder.py
parentmove get_all_pushers call down (diff)
downloadsynapse-c7273c11bc73630e3f2ab1a82d20a40d8b17f9a3.tar.xz
Give pushers their own background logcontext
Each pusher has its own loop which runs for as long as it has work to do. This
should run in its own background thread with its own logcontext, as other
similar loops elsewhere in the system do - which means that CPU usage is
consistently attributed to that loop, rather than to whatever request happened
to start the loop.
Diffstat (limited to 'synapse/events/builder.py')
0 files changed, 0 insertions, 0 deletions