Architectural Changes In New V8 versions
summary
Explains V8 pipeline changes with concrete numbers and microbenchmarks: Ignition produces bytecode, TurboFan generates optimized binaries that expect consistent types so monomorphic functions run fastest and deopt jumps a 6.5ms case to ~8ms (~40% slower). New sparkplug produces non‑optimized machine code for every bytecode, cutting a cold start from ~1s to ~40ms (~40% improvement). ES modules let the parser load only needed exports instead of blocking require. Class property inline caching reduces a hot loop from 3.2ms to 2.7ms (~30% gain).
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:21Code Parsing Pipelines
- 2:17Ignition Interpreter
- 2:36Turbofan Compiler - JIT Compiler
- 4:49Optimization And De-Optimization
- 8:32De-Optimization - Wrong Map
- 12:04What Needs Improvement?
- 12:49V8 New Architecture - Mid Tier Compiler
- 13:25Before Adding SparkPlug
- 14:00After Adding SparkPlug
- 14:27Ignition Does The Hard Work
- 15:15SparkPlug Real World Performance Improvement
- 20:43JavaScript Objects
- 23:16The Solution - The Inline Cache
- 25:08Benchmark Code
related talks
33mJavaScript: The V8 Engine optimization tips (...)
23mJoin the super secret V8 club & become a JavaScriptbender
28mV8 and How It Listens to You
22mHigh Performance JS in V8
32mV8 by example: A journey through the compilation pipeline
01h 00mV8 Under the Hood
26mPractical Optimization for V8
25mJavaScript engines how do they even?