Chrome V8

Developer(s) The Chromium Project
Initial release September 2, 2008 (2008-09-02)
Stable release
6.7[1] / May 4, 2018 (2018-05-04)
Written in C++,[2] JavaScript[2]
Platform IA-32, x86-64, ARM, MIPS,[3] PowerPC, IBM s390
Type JavaScript engine
License BSD[4]

Chrome V8, or simply V8, is an open-source JavaScript engine developed by The Chromium Project for Google Chrome and Chromium web browsers.[5] The project’s creator is Lars Bak.[6] The first version of the V8 engine was released at the same time as the first version of Chrome: September 2, 2008. It has also been used in Couchbase, MongoDB and Node.js that are used server-side.

V8 compiles JavaScript directly to native machine code before executing it, instead of more traditional techniques such as interpreting bytecode or compiling the whole program to machine code and executing it from a filesystem. The compiled code is additionally optimized (and re-optimized) dynamically at runtime, based on heuristics of the code's execution profile. Optimization techniques used include inlining, elision of expensive runtime properties, and inline caching. The garbage collector is a generational incremental collector.[7]

V8 can compile to x86, ARM or MIPS instruction set architectures in both their 32- and 64-bit editions; as well, it has been ported to PowerPC[8] and IBM s390[9][10] for use in servers.[3][11]


The V8 assembler is based on the Strongtalk assembler.[12] On 7 December 2010, a new compiling infrastructure named Crankshaft was released, with speed improvements.[13] Since version 41 of Chrome in 2015, project TurboFan has been added to enable more speed, e.g. for asm.js.[14]

In 2016, the Ignition interpreter was added to V8 with the design goal of reducing the memory usage on small memory Android phones in comparison with TurboFan and Crankshaft.[15]

In 2017, V8 shipped a brand-new compiler pipeline, consisting of Ignition (the interpreter) and TurboFan (the optimizing compiler). Starting with V8 version 5.9, Full-codegen and Crankshaft are no longer used in V8 for JavaScript execution, since the team believes they are no longer able to keep pace with new JavaScript language features and the optimizations those features require.[16]


V8 is intended to be used both in a browser and as a standalone high-performance engine that can be integrated into independent projects. V8 is used in the following software:

See also


  1. "V8 Release v6.7". V8 Project.
  2. 1 2 "V8 JavaScript Engine". Google Code.
  3. 1 2 "Introduction - Chrome V8". Google Developers.
  4. "v8/LICENSE.v8 at master". Github.
  5. Lenssen, Philipp (1 September 2008). "Google on Google Chrome - comic book". Google Blogoscoped. Google. Retrieved 17 August 2010.
  6. Minto, Rob (27 March 2009). "The genius behind Google's web browser". Financial Times. Retrieved 17 August 2010.
  7. "A game changer for interactive performance". Chromium Blog. Google. Retrieved 1 May 2012.
  11. "V8 Changelog v3.8.2". Google. Retrieved 23 October 2012.
  12. "V8 JavaScript Engine: License". Google Code. Google. Archived from the original on July 22, 2010. Retrieved 17 August 2010.
  13. "A New Crankshaft for V8". Chromium Blog. Google. 7 December 2010. Retrieved 22 April 2011.
  14. "Revving up JavaScript performance with TurboFan". 7 July 2015. Retrieved 5 March 2016.
  15. "BlinkOn 6 Day 1 Talk 2: Ignition - an interpreter for V8". 26 June 2016. Retrieved 2 September 2016.
  16. "Launching Ignition and TurboFan". 16 May 2017. Retrieved 13 July 2017.
  17. Jolie O'Dell (March 10, 2011). "Why Everyone Is Talking About Node". Mashable.
  18. "NativeScript Android Runtime Overview".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.