DevTools/Performance/JIT: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with " == Overview == When approaching the upper bounds of squeezing out performance, the more relevant the platform details become. We want to expose engine-level information on...")
 
No edit summary
Line 16: Line 16:
* Optimizing new ES.* features in Spider Monkey
* Optimizing new ES.* features in Spider Monkey
* Finding how to optimize hot areas of code (advanced usage)
* Finding how to optimize hot areas of code (advanced usage)
  Frameworks (React, Ember, PlayCanvas, jQuery, Three.js)
Frameworks (React, Ember, PlayCanvas, jQuery, Three.js)
  Environments (Shumway, J2ME.js)
Environments (Shumway, J2ME.js)
  SIMD?
SIMD?
* Ensuring functions stay at the highest level of optimization (more important than using better optimization strategies per optimization site)
* Ensuring functions stay at the highest level of optimization (more important than using better optimization strategies per optimization site)
* Guide web developers to optimize their web app with low-hanging-fruit, without needing engine knowledge
* Guide web developers to optimize their web app with low-hanging-fruit, without needing engine knowledge
Line 62: Line 62:
* [http://mrale.ph/irhydra/2/ IRHydra (V8, Dart)]
* [http://mrale.ph/irhydra/2/ IRHydra (V8, Dart)]
* [https://developer.chrome.com/devtools/docs/cpu-profiling Chrome DevTools (V8)]
* [https://developer.chrome.com/devtools/docs/cpu-profiling Chrome DevTools (V8)]
  No documentation regarding the deopt icons, and the tooltips they use are still pretty cryptic; some deopts I've seen:
No documentation regarding the deopt icons, and the tooltips they use are still pretty cryptic; some deopts I've seen:
   Reference to a variable that requires dynamic lookup
   Reference to a variable that requires dynamic lookup
   ForInStatement is not fast case
   ForInStatement is not fast case
Confirmed users
110

edits

Navigation menu