19 Apr '13, 4pm

@ofcourseiam sorry the docs got out of date, try 'require "tooling/profiler/profiler"' with this /c @dbussink

In Ruby land, the Rubinius::Profiler::Instrumenter instance exposes nothing about the multi-threaded reality in the VM. The individual C++ Profiler instances are not exposed to Ruby. In Ruby, a profiler instance is created. That instance can simply start and stop the VM profiler. When the profiler is stopped, info about the profiling is returned in a LookupTable. The Ruby profiler code can display that info using the #show method.

Full article: http://rubini.us/doc/en/tools/profiler/


Today, I really feel sorry for you

harismibrahim.wordpress.com 18 Apr '13, 4am

I am writing this as a voter and as an active PAS member residing in Kajang. Me and many of my friends who have been activ...