6a78ede569
The existing implementation of the `python_twisted_reactor_tick_time` metric is pretty useless, because it *only* measures the time taken to execute timed calls and callbacks from threads. That neglects everything that happens off the back of I/O, which is obviously quite a lot for us. To improve this, I've hooked into a different place in the reactor - in particular, where it calls `epoll`. That call is the only place it should wait for something to happen - the rest of the loop *should* be quick. I've also removed `python_twisted_reactor_pending_calls`, because I don't believe anyone ever looks at it, and it's a nuisance to populate. |
||
|---|---|---|
| .. | ||
| cmdclient | ||
| docker | ||
| experiments | ||
| grafana | ||
| graph | ||
| jitsimeetbridge | ||
| prometheus | ||
| purge_api | ||
| scripts | ||
| systemd | ||
| systemd-with-workers | ||
| vertobot | ||
| README.rst | ||
| example_log_config.yaml | ||
README.rst
Community Contributions ======================= Everything in this directory are projects submitted by the community that may be useful to others. As such, the project maintainers cannot guarantee support, stability or backwards compatibility of these projects. Files in this directory should *not* be relied on directly, as they may not continue to work or exist in future. If you wish to use any of these files then they should be copied to avoid them breaking from underneath you.