Firefox memory usage high

broken image
broken image

Hopefully I’ve convinced you we’ve put a lot of work into performance, now let’s see how we’re doing memory-wise compared to other browsers. Some great work has been happening lately to reduce Stylo's memory usage.

broken image

The Stylo team was a big user of this and it shows, we flipped the switch to enable Stylo by default around the 7th and you can see a fairly large regression, but by the 16th it was mostly gone: Luckily since we brought AWSY in tree it’s been pretty easy to track memory usage and regressions even on separate development branches. We’ve quantum-ed all the things but we haven’t really talked about memory usage, which is something that often falls by the wayside in the pursuit of performance.

broken image

For background see my previous installment.įirefox’s upcoming release 57 has a huge focus on performance. This is a continuation of my Are They Slim Yet series.