You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
doing
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!
The text was updated successfully, but these errors were encountered: