Re: [JS-internals] Tracelogging revived

2013-07-20 Thread Till Schneidereit
On Sat, Jul 20, 2013 at 1:43 AM, wrote: > On Friday, July 19, 2013 1:27:30 AM UTC-7, David Bruant wrote: > > Any chance this could be made into an addon (or just Firefox devtools)? > > Something like : reload the page to get the graphs. > > How is the information exposed? (so I understand how an

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

Re: [JS-internals] Tracelogging revived

2013-07-18 Thread Nicholas Nethercote
> 2) There is something strange going on with Splay GGC. We could be much > faster on it. It seems like we are stuck in baseline on splay.js:49 for a lot > of time! That function is doing nothing but returning a value, but somehow > that takes 25% of the execution time (excluding gc). I guess so

[JS-internals] Tracelogging revived

2013-07-18 Thread hv1989
I took the time to get tracelogging up and running again and create V2 out of it. I think most know tracelogging already, but for those that don't: Tracelogging traces when which scripts runs and which engine we use for it. Out of the log information I create graphs showing when which engine is