Extreme JavaScript Performance
summary
Argues concrete micro-optimizations with measurements: inlining function calls and inlining instead of repeated calls removes call overhead, unrolling loops yields 2x–5x speedup in examples, coercing strings to integers with bitwise ops beats parseInt, caching globals helps some engines, and using try/catch or with forces slower fallback code making some engines ~10x slower under JIT. Benchmarks run in JS with new Date().getTime for 100k–1M iterations and Closure compiler sometimes breaks code.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:00Performance
- 3:00Speed
- 4:00Function Calls
- 6:00IE Performance
- 7:00Embrace the language
- 8:00Performance comparison
- 12:00Loops
- 16:00IE
- 17:00Beef Statement
- 18:00Trycatch
- 19:00Modern engines
- 20:00Strict mode
- 22:00JavaScript introspection
- 24:00JavaScript book
- 25:00JavaScript measurements
- 26:00JavaScript benchmark functions
- 27:00Optimization tools
- 28:00Google Closure
related talks
31mJavaScript Compilation Techniques or "Wasn't JavaScript supposed to be slow?"
29mJavaScript Engines: How Do They Even?
46mHow much performance can you get out of JavaScript?
33mJavaScript: The V8 Engine optimization tips (...)
16mJavaScript & Metaperformance
25mJavaScript engines how do they even?
39mHow much performance can you get out of Javascript?
41mBenchmarking JavaScript