A Decade of V8: Milestones, Performance Evolution, and Future Outlook

In celebration of both Chrome’s and V8’s 10‑year anniversaries, this article provides an overview of the major milestones of V8 over the past decade.

Before V8 Open‑Source

In the fall of 2006, Google hired Lars Bak to build a new JavaScript engine for Chrome, initially a secret internal project. After moving back to his farm in Aarhus, Denmark, the early team named the engine “V8” to evoke a powerful car engine, later relocating to a modern office as the team grew.

V8 Open‑Source and Continuous Improvement

On September 2, 2008, Chrome was released and V8 was officially open‑sourced; the first commits date back to June 30, 2008. Early V8 supported ia32 and ARM and used SCons for building. Subsequent years saw the addition of new features such as the Irregexp regex engine (2009), x64 support, the Crankshaft JIT (2010), incremental garbage collection and isolates (2011), and the transition from SCons to GYP.

Benchmarking became a focus in 2012 with Sunspider, Kraken, and later Octane, driving performance‑focused optimizations. In 2013, asm.js and the Handle API rewrite were introduced, and TypedArrays moved from Blink to V8.

2014 brought concurrent compilation, the first TurboFan prototype, and porting to PPC, MIPS64, and ARM64, along with a migration from SVN to Git. In 2015 V8 added code caching, script streaming, and the first WebAssembly prototype.

2016 saw the release of ES2015/ES2016 features, the Ignition interpreter, TurboFan pipeline, the Orinoco parallel garbage collector, and WebAssembly experimental support. V8 also won the ACM SIGPLAN Programming Languages Software Award and added S390 support.

In 2017 the engine was refactored to use Ignition and TurboFan by default, removing Crankshaft, and Orinoco v1.0 was launched. Node.js became a first‑class V8 embedder, and fuzz testing infrastructure was added.

V8 now fully supports WebAssembly, ES2017/ES2018 features, JavaScript modules, and native code coverage. Security research in 2018 addressed Spectre/Meltdown side‑channel attacks, adding mitigations for untrusted code.

Recent work includes the Liftoff baseline compiler for WebAssembly, the BigInt primitive, delayed deserialization of built‑in functions, background bytecode compilation, and the Unified V8‑Blink heap project.

Performance Fluctuations of V8

V8 Bench scores from 2008‑2018 show a four‑fold increase, with two notable regressions: in 2015 due to ES2015 feature integration, and in early 2018 because of Spectre‑related mitigations. A plateau around 2013 reflects a shift from synthetic micro‑benchmarks (V8 Bench, Octane) to real‑world performance metrics such as Speedometer 1, which rose fourfold in the same period.

Summary

Although V8 originated for Chrome, it has become an independent project with its own codebase and embedding API, powering both web browsers and environments like Node.js. Over ten years it expanded from two instruction sets to eight, migrated build systems from SCons to GYP to GN, and evolved its compilation pipeline from Full‑codegen and Crankshaft to Ignition and TurboFan, while adding WebAssembly support and advancing JavaScript language features up to ES2018 and beyond.

The web’s story continues, and V8, JavaScript, and WebAssembly will remain key players for many years to come.