One of the reasons was that the Chrome engineers saw that a change was happening in hardware and they started making better use of that new hardware.Ī new style of CPU was becoming popular. Chrome was faster and more responsive than Firefox when it was first introduced. To get faster, we needed to take advantage of the way hardware has changed over the past 10 years. Laying the foundation with coarse-grained parallelism So, let’s look at how Firefox got fast again and where it’s going to get faster. It doesn’t mean that today’s Firefox is as fast and responsive as it’s going to be. We call this Project Quantum, and the first general release of the reborn Firefox Quantum comes out tomorrow.īut this doesn’t mean that our work is done. Plus, we’ve had a browser performance strike force scouring the codebase for performance issues, both obvious and non-obvious. Over the past seven months, we’ve been rapidly replacing major parts of the engine, introducing Rust and parts of Servo to Firefox.
People have noticed that Firefox is fast again.
