How much performance can you get out of Javascript?

on YouTube ↗39m

" summary

Measures raw CPU-bound work by finding 25,000 primes, comparing a like-for-like C++ baseline to JavaScript on V8. Initial JS runs ~4× slower, but after fixing a bounds bug, preallocating arrays, stabilizing hidden classes and types, and using Ignition and Turbofan optimizations JS approaches native speed (within ~45%), while adding type hints yields ~10% gain and a better algorithm gives ~30× speedup. Uses V8 tracing/profiler and Chrome flags; use WebAssembly only when JS semantics limit performance.

AI-written summary · about

" chapters (8)

1. 0:00Introduction and background
2. 5:51How V8 optimizes JavaScript
3. 16:50Hidden classes and type tracking
4. 22:10TurboFan and optimizing compiler
5. 27:52Avoiding optimization pitfalls
6. 31:03Benchmarking and real-world fixes
7. 34:20Performance comparison with C++
8. 37:13Q&A

" related talks

• 46mHow much performance can you get out of JavaScript?Massimiliano Mantione · jsDay 2017
• 27mSpeed, Speed, Speed: JavaScript vs C++ vs WebAssemblyFranziska Hinkelmann · International JavaScript Conference Munich 2019
• 27mSpeed, Speed, Speed: Javascript vs C++ vs WebAssemblyFranziska Hinkelman · NodeConf Argentina 2018
• 16mJavaScript & MetaperformanceDouglas Crockford · Velocity 2011
• 29mExtreme JavaScript PerformanceThomas Fuchs · JSConf.eu 2009
• 34mUnderstanding JavaScript PerformanceGodfrey Chan · EmberConf 2017
• 31mJavaScript Compilation Techniques or "Wasn't JavaScript supposed to be slow?"Marijn Haverbeke · JSConf US 2011
• 30mNative Speed on the Web: JavaScript and asm.jsAlon Zakai · Strange Loop 2013