High Performance JS in V8
summary
Explains why V8 replaces Crankshaft with the Ignition and Turbofan pipeline, showing concrete tradeoffs: Crankshaft produces brittle performance cliffs (examples of 10x and a headline 19x faster across versions), lacks full-language support so try/catch, rest arguments and newer ES6 features forced hacks, and microbenchmarks mislead. Describes real code fixes (rest parameters become optimizable), measurable improvements, and deployment status (already in Chrome and shipping in Node 8 LTS), so worth watching if engine-level, actionable performance details matter.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:57What is an Engine, Anyway?
- 5:38What was Crankshaft?
- 7:21Problems with Crankshaft
- 10:40Crankshaft Performance Advice
- 14:14CrankshaftScript 3
- 17:07Fast JS for Turbofan
- 18:05Returning Arguments - Crankshaft
- 19:08Returning Arguments - TurboFan
related talks
16mJavaScript & Metaperformance
01h 00mV8 Under the Hood
29mJavaScript Engines: How Do They Even?
23mJoin the super secret V8 club & become a JavaScriptbender
17mV8 engine, JS Code Interpretation, and Execution
33mJavaScript: The V8 Engine optimization tips (...)
48mV8 Meets the Enemy
57mWarm up your engine! or I know what you did last summer to V8 (UK)