6e3fc657b4
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. |
||
|---|---|---|
| .. | ||
| transport | ||
| __init__.py | ||
| federation_base.py | ||
| federation_client.py | ||
| federation_server.py | ||
| persistence.py | ||
| send_queue.py | ||
| transaction_queue.py | ||
| units.py | ||