That worked. Here's the output plus the program that created it. http://gist.github.com/372919
In my cursory inspection of the output, it looks like Array#inspect and String::Unpacker#dispatch takes a LOT of time. If you notice a few things that need some love, post them back and I'll take a look. cr On Apr 20, 2010, at 1:58 PM, Evan Phoenix wrote: > Hi Chuck, > > On Apr 20, 2010, at 11:51 AM, Chuck Remes wrote: > >> I checked the website (rubini.us) for some guidance on how to profile ruby >> code under rbx, but I came up empty. > > Check out http://github.com/evanphx/rubinius/blob/master/doc/profiling.txt. > We should figure out a way to put all the stuff in doc/ directly on the > website. > > The short answer is to do: > > rbx -Xint -P <file> > > or > > rbx -Xint -Xprofiler.graph -P <file> > > The -Xint is required because the profiler inside JIT'd methods is currently > not working properly. > > The -Xprofiler.graph will show the full call graph profiling instead of the > flat profiling info. > > If you run these on your code and post the results, I'll have a look. > > - Evan > >> I would be grateful for any pointers. Thanks... >> >> cr >> >> -- >> --- !ruby/object:MailingList >> name: rubinius-dev >> view: http://groups.google.com/group/rubinius-dev?hl=en >> post: [email protected] >> unsubscribe: [email protected] >> > > -- > --- !ruby/object:MailingList > name: rubinius-dev > view: http://groups.google.com/group/rubinius-dev?hl=en > post: [email protected] > unsubscribe: [email protected] -- --- !ruby/object:MailingList name: rubinius-dev view: http://groups.google.com/group/rubinius-dev?hl=en post: [email protected] unsubscribe: [email protected]
