Hi Trevor, Thanks a lot. It works.
I'm trying to profile synchronous and asynchronous code. The flame graph for synchronous code is very clear because you can see all the stack of functions, just as in the code. This makes trivial to, from the graph, finding the involved code. However, apparently the flames for asynchronous code are always contained within "emit events.js:68", without a reference to the original "user" caller code. I've tried to give a name to the anonymous functions I had in there just in case that helps, but it does not. These new names appear on the SVG source code but not containing anything, so their width is sub-pixel. So, do you know of a technique to know which are the functions that provoke the call to async code? So for example, the name of the caller would be included on the "emit events.js" spans, or on their first child. I hope the question makes sense. Thank you. On Sunday, June 15, 2014 6:07:23 AM UTC+2, Trevor Norris wrote: > > If you're using master the you don't have to use dtrace. I have a rough > outline here of how to create flame graphs: > https://gist.github.com/trevnorris/9616784 -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/403691b9-a674-422f-b510-5b87665f629d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
