The Footprint of Performance
summary
Modern JavaScript VMs get speed by adding hidden classes, inline caching, an optimizing compiler and an incremental low‑pause GC, and those optimizations inflate memory via overallocated object slots and backing stores. v8’s slack tracking forces extra slots; turning a hot point type into two constructors cuts heap use in a ray tracer by 40% less memory. Array literals let v8 share a copy-on-write backing store; moving bulky values out of outer scopes removes context‑allocated bloat.
AI-written summary · about
chapters (7)
- 0:00Introduction to V8
- 1:04Engine overview and goals
- 3:22Optimization methodology
- 5:21Object memory representation
- 12:57Array memory management
- 17:52Execution context and closures
- 23:00Q&A and concluding thoughts
related talks
33mJavaScript: The V8 Engine optimization tips (...)
31mJavaScript memory management: Visual Guide
27mVisualised guide to memory management in JavaScript
23mWarp Speed Memory Management
30mMemory Don't Forget To Take Out The Garbage
26mJavaScript VMs 101
28mPerformance Profiling for V8
26mThe Hitchhiker's Guide to All Things Memory in Javascript