Volume on this list is low enough that I'm going to use it as a backup brain for a few requests.
PROFILER 1. A good chunk of the C-api in Rubinius is implemented as a rb_funcall back into a pure Ruby path. None of these paths show up during profiling. It would be great if they did show up so that it is easier to identify "slow paths" in C extensions. 2. On hydra (no-GIL branch) it would be interesting if there were an additional cli flag (-Xprofiler.by_thread ?) that would separate the statistics by thread. This sounds difficult, but it would be a helpful tool for identifying "hot" threads in a multi-threaded app. Additionally, it could probably help identify hot methods / bottlenecks where multiple threads come together for synchronization. That's all for the moment. cr -- --- !ruby/object:MailingList name: rubinius-dev view: http://groups.google.com/group/rubinius-dev?hl=en post: [email protected] unsubscribe: [email protected]
