anonymousland-synapse/synapse/federation
Richard van der Hoff 6e3fc657b4 Resource tracking for background processes
This introduces a mechanism for tracking resource usage by background
processes, along with an example of how it will be used.

This will help address #3518, but more importantly will give us better insights
into things which are happening but not being shown up by the request metrics.

We *could* do this with Measure blocks, but:
 - I think having them pulled out as a completely separate metric class will
   make it easier to distinguish top-level processes from those which are
   nested.

 - I want to be able to report on in-flight background processes, and I don't
   think we want to do this for *all* Measure blocks.
2018-07-18 10:50:33 +01:00
..
transport run isort 2018-07-09 16:09:20 +10:00
__init__.py Remove unused ReplicationLayer 2018-03-13 11:00:04 +00:00
federation_base.py rename assert_params_in_request to assert_params_in_dict 2018-07-13 21:53:01 +02:00
federation_client.py run isort 2018-07-09 16:09:20 +10:00
federation_server.py run isort 2018-07-09 16:09:20 +10:00
persistence.py run isort 2018-07-09 16:09:20 +10:00
send_queue.py run isort 2018-07-09 16:09:20 +10:00
transaction_queue.py Resource tracking for background processes 2018-07-18 10:50:33 +01:00
units.py run isort 2018-07-09 16:09:20 +10:00