Re: [JS-internals] Tracelogging revived

2013-07-19 Thread hv1989
On Friday, July 19, 2013 7:37:28 AM UTC-7, Luke Wagner wrote: > One thing that I think would be really informative is how much time is spent > in C++ stubs called from the baseline/ion. They happen frequently enough > that you probably wouldn't want them to be interleaved on the graph, but > ma

Re: [JS-internals] Tracelogging revived

2013-07-19 Thread Luke Wagner
This is really really cool! One thing that I think would be really informative is how much time is spent in C++ stubs called from the baseline/ion. They happen frequently enough that you probably wouldn't want them to be interleaved on the graph, but maybe the time could be summed and attached

Re: [JS-internals] Tracelogging revived

2013-07-19 Thread David Bruant
Hmm... HOLY SHIT THIS IS AWESOME !!! 2013/7/19 > I also created a python script to get some meaningful information out of > it. Nice graphs ;). But actually much more info can get out of it. It's > that file I used to profile octane and find problems in it. The python > script that create nice

Re: [JS-internals] Tracelogging revived

2013-07-19 Thread Till Schneidereit
These graphs look amazing! I'm very much looking forward to doing them for Shumway: I'm sure we can glean some info from them about how to optimize that codebase, itself. Three quick comments on the UI: - the roll out to the bottom from the graph doesn't work, so the block-tooltips stay around if