https://v8.dev/blog/ignition-interpreter https://v8.dev/blog/ignition-interpreter "V8 team has built a new JavaScript interpreter, called Ignition, which can r

https://v8.dev/blog/ignition-interpreter https://v8.dev/blog/ignition-interpreter "V8 team has built a new JavaScript interpreter, called Ignition, which can replace V8’s baseline compiler, executing code with less memory overhead and paving the way for a simpler script execution pipeline." https://v8.dev/blog/preparser https://v8.dev/blog/preparser "Lazy parsing speeds up startup and reduces memory overhead of applications that ship more code than they need." https://v8.dev/blog/embedded-builtins https://v8.dev/blog/embedded-builtins "V8 built-in functions (builtins) consume memory in every instance of V8. The builtin count, average size, and the number of V8 instances per Chrome browser tab have been growing significantly. This blog post describes how we reduced the median V8 heap size per website by 19% over the past year." https://v8.dev/blog/improved-code-caching https://v8.dev/blog/improved-code-caching "V8 uses code caching to cache the generated code for frequently-used scripts. Starting with Chrome 66, we are caching more code by generating the cache after top-level execution. This leads to a 20-40% reduction in parse and compilation time during the initial load." Etc, etc.