MatrixSynapse/synapse/push
Richard van der Hoff c7273c11bc 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.
2018-10-22 16:12:11 +01:00
..
__init__.py
action_generator.py
baserules.py
bulk_push_rule_evaluator.py
clientformat.py
emailpusher.py Give pushers their own background logcontext 2018-10-22 16:12:11 +01:00
httppusher.py Give pushers their own background logcontext 2018-10-22 16:12:11 +01:00
mailer.py
presentable_names.py
push_rule_evaluator.py
push_tools.py
pusher.py
pusherpool.py move get_all_pushers call down 2018-10-22 16:12:11 +01:00
rulekinds.py