On Wed, Apr 11, 2012 at 9:55 AM, Ben Noordhuis <i...@bnoordhuis.nl> wrote:
> > I mean when the profiler wakes up, it would look at a call trace right? > Are > > the lines logged in the JS section at the top of the stack? > > This can be misleading since the call stack might have changed due to > > setTimeouts. I want to understand how can I interpret these lines and > what > > are its caveats. > > That's how sample-based profiling works: you trade accuracy for efficiency. > > Here's a GSoC project for you: augment callgrind to understand the > code V8 generates. I'll buy you a beer if you do. :-) > Couldn't a much more accurate profiler be built using the debugger hooks? It would be massively slower but should be 100% accurate and allow line-by-line profiling like perl's Devel::NYTProf. Matt. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
