-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to visualize profiling info from v8 profiler #196
Comments
I think so! Can you add a screenshot here of how that would look like?
I think because we need no native addon to start that. @davidmarkclements definitely knows more! |
Yeah sure. Here is a flamegraph of a simple server responding with a string To run it you simply invoke:
I was more interested in the profiling data that is provided. Does |
@slonka send the PR over. In your PR can you please add an example on how to generate that output?
I never investigated in depth. The actual output looks very similar anyway. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Hi,
V8 profiler has methods called StartProfiling, StopProfiling (https://v8docs.nodesource.com/node-10.6/d2/d34/classv8_1_1_cpu_profiler.html#ab78880137fc43d636cca23c81567b52d). There are modules that allow accessing these methods: https://github.com/hyj1991/v8-profiler-next/blob/master/src/cpu_profile.cc. I created a converter that can convert that format into something that is acceptable by 0x (generates a tree structure similar to the one generated here: https://github.com/davidmarkclements/0x/blob/master/lib/render.js#L19).
Would you be interested in including that functionality? (you can preview the code here: slonka@a9c848c and I'll create a PR if you want)
BTW I'm just wondering why did you only use
--prof
as a means of collecting stack information? How does it differ fromCpuProfiler::StartProfiling
?The text was updated successfully, but these errors were encountered: