mirror of
https://github.com/xcat2/confluent.git
synced 2024-11-25 19:10:10 +00:00
8fa8951896
To do performance optimization in this sort of application, this is about as well as I have been able to manage in python. I will say perl with NYTProf seems to be significantly better for data, but this is servicable. I tried yappi, but it goes wildly inaccurate with this codebase. Because of the eventlet plumbing, cProfile is still pretty misleading. Best strategy seems to be review cumulative time with a healthy grain of salt around the top items until you get down to info that makes sense. For example, trampoline unfairly gets a great deal of the 'blame' by taking on nearly all the activity. internal time seems to miss a great deal of important information. |
||
---|---|---|
.. | ||
confetty | ||
confluent-server.py | ||
nodepower |