Ad Blocking Extensions Tested for Performance
They didn't seem to know about e10s in Firefox Nightly which would have solved their "no separate process" thing.<p>Measuring peak CPU is very, very stupid. The best Ad Blocker should have near 100% CPU but for an extremely short amount of time. Using 100% CPU is making the most efficient use of the hardware, not being inefficient. Now, I think due to the way they're measuring, it's actually closer to being average CPU because task manager samples over a period.<p>Also: "Firefox didn’t like this page at all and we couldn’t get consistent readings to run tests, on every refresh the browser would simply not respond or crash."<p>Huh? I think somethings wrong there. Firefox obviously renders tmz.com. A bug in the thing they used to monitor page load times? Did they check the performance impact of it?