Adding Ignition to the script execution pipeline opens up the possibilities beyond decreasing V8 memory overhead. According to MCllory "The Ignition pipeline has been designed to allow us to make smarter decisions about when to execute and optimise code to speed up loading web pages and decrease jank and to build the interchange between v8's various components more efficient".
V8 and other engines control JiT compilation scripts to native machine code. The script execution pipeline has conditions requiring complex machinery to switch between the baseline compiler and other optimising compilers: CrankShaft and Turbofan.
If the code is executed only once,"JiTed" machine code can consume lots of memory even with this process. Ignition will be able to execute codes with less memory overhead which will result in simpler script execution.
Low-level instructions from Turbofan will be used to generate bytecode handlers for opcodes. The function of TurboFan is to compile the instructions to the target architecture. Low-level instruction selection and machine register allocation will be achieved through this method. McIlroy explained,"This produces highly optimized interpreter code, which can execute the bytecode instructions, and communicate with the rest of the V8 virtual machine in a low-overhead manner".
McIlroy also said that Android devices with 512MB of memory will be able to allow Ignition. "Results from initial experiments in the field show that Ignition decreases the memory of each Chrome tab by around 5 percent”.