search

thlorenz / deoptigate

⏱️ Investigates v8/Node.js function deoptimizations.
https://nodesource.github.io/deoptigate-examples/xml2js/01_start/?selectedFileIdx=31&selectedLocation=157&includeAllSeverities=false&highlightCode=true&selectedTabIdx=1&selectedSummaryTabIdx=1
MIT License
1.15k stars 22 forks source link

no deopts in visualization, but plenty in `--trace-deopt` output? #30

Open softwareCobbler opened 2 years ago

softwareCobbler commented 2 years ago

doing

~$ node -v
16.13.2
~$ node --trace-deopt --prof app
~$ deoptigate

writes the --trace-deopt output to the console, and the --prof generates the log file that deoptigate builds its visualization from. Chrome pops up and renders out the visualization, so far so good!

But, in the visualization, there are no deoptimizations listed, whereas the --trace-deopt output has plenty of (~100) deoptimizing [address] <JSFunction> ....

I'm not sure if I'm using the tool correctly, but I was expecting deoptigate to render a visualization of the same deoptimizations that --trace-deopt detects (which is what led me here, I don't know enough about v8 internals to use the raw --trace-deopt output for any perf gains, figured a visualization would point to "this property access triggers deopt" or etc.).

thanks for your time!

feedthejim commented 1 year ago

FWIW I've had the same issue.