What's Happening in V8?
summary
V8's recent changes reduce baseline memory use by about 15% on typical workloads through a new heap and collector plus fixes for mobile and Chrome OS sandboxes, and a new property-shape/offset scheme that stores property offsets instead of names to shrink object size. The update also includes significant JSON parsing speedups and streaming/compile-on-demand tooling to cut parse time, and it adds usable WebAssembly and first-class async/await support for Node with implementation details and benchmarked measurements.
AI-written summary · about
chapters (8)
- 0:00V8 memory challenges
- 3:21Memory hierarchy and caching
- 8:28Optimizing V8 memory
- 13:31Chrome OS sandbox limits
- 16:52JS object shape optimization
- 20:59Streaming JS for faster loads
- 23:38Chrome 7+ performance
- 26:43V8 and DevTools future
related talks
23mWhat’s new in V8/JavaScript
24mDemystifying V8 and JavaScript Performance
30mV8 internals for JS developers
33mJavaScript: The V8 Engine optimization tips (...)
17mV8 engine, JS Code Interpretation, and Execution
57mWarm up your engine! or I know what you did last summer to V8 (UK)
26mArchitectural Changes In New V8 versions
22mHigh Performance JS in V8