3 ms·
I think any kind of visualisation of VMs like you're suggesting (little hazard symbol next to deoptimised methods) is very complicated in practice. A method co
by chrisseaton 11y ago
I think any kind of visualisation of VMs like you're suggesting (little hazard symbol next to deoptimised methods) is very complicated in practice.
A method could be deoptimised once early, but then not again when the program is actually running in your inner loop. In which case you don't care it was deoptimised.
In the optimising implementation of Ruby I work on, we are aggressive about splitting (multiple versions of a method so they can collect independent profiling data) and that means one version of a method may be deoptimised, but others aren't. How do you show that when you are looking at a single copy of the source code?
- netghost 11y agoChrome Canary at least is now showing deopt next to functions in the profiler.