-
Notifications
You must be signed in to change notification settings - Fork 77
Firefox version: benchmarking memory footprint (2015 03 07)
Infamous VIM test: ABP 1,900 MB vs. uBlock 392 MB. Firefox 35 64-bit. ABP systematically adds around 3.5 MB per page and per-frame on a page, when using only EasyList.
- Ensure the blocker is the only active extension (to avoid results to be polluted by other extensions)
- Ensure click-to-play (or whatever equivalent) is enabled before launching the benchmark
- Select the following filter lists in the benchmarked blockers:
- EasyList
- Peter Lowe's Ad server list
- EasyPrivacy
- Fanboy's Social Blocking List
- Malware domain lists
- ABP-specifics: "Acceptable ads" disabled
- uBlock-specifics: uBlock's filters enabled (+80 filters), extra malware domains (+1,459 filters)
- Have the benchmarked blocker enabled and properly setup
- Have only the "new tab" opened
- Quit Firefox
- Launch Firefox
- Paste http://news.yahoo.com/ in address bar, wait for page to finish loading
- Open new tab, paste http://news.google.com/, wait for page to finish loading
- Open new tab, paste http://www.huffingtonpost.com/, wait for page to finish loading
- Open new tab, paste http://www.cnn.com/, wait for page to finish loading
- Open new tab, paste http://www.nytimes.com/, wait for page to finish loading
- Open new tab, paste http://www.foxnews.com/, wait for page to finish loading
- Open new tab, paste http://www.nbcnews.com/, wait for page to finish loading
- Open new tab, paste http://www.dailymail.co.uk/, wait for page to finish loading
- Open new tab, paste http://www.washingtonpost.com/, wait for page to finish loading
- Open new tab, paste http://www.theguardian.com/, wait for page to finish loading
- Open new tab, paste https://news.ycombinator.com/, wait for page to finish loading
- Leave the browser idle for two minutes
- Open new tab, paste
about:memory
, wait for page to finish loading - Firefox: Click "Minimize memory usage" button in "Free memory" section
- Firefox: Click Measure button in "Show memory reports" section
- Firefox: Write down "Explicit Allocations" value (see notes below) / Chromium: Write down Σ value
So I did the exact above steps for no blocker, ABP, uBlock.
-
Firefox
- No blocker: 613.55 MB (reference memory usage)
- Adblock Plus 2.6.6: 625.05 MB (reference plus 11.5 MB)
- µBlock 0.8.2.0: 426.85 MB (reference minus 186.7 MB, ABP minus 198.2 MB)
-
Chromium
- No blocker: 1,169.35 MB (reference memory usage)
- Adblock Plus 1.8.8: 1,509.05 MB (reference plus 339.7 MB)
- µBlock 0.8.2.0: 1,042.94 MB (reference minus 126.41 MB, ABP minus 466.11 MB)
Important: You can't compare directly the figures between the browsers -- they are taken using different methodology from one browser to the other. The benchmarks are more to compare the figures for various blockers within the same browser.
Tested on Firefox 34 64-bit and Chromium 39 64-bit on Linux Mint. No other extensions were present.
For Firefox, I chose the "Explicit Allocations" figure because as per Firefox, it is "the single best number to focus on" with regard to memory usage.
Without going into details, hardware is i5 quadcore + 8 GB
If other users feel like repeating the tests, it would be nice just to confirm I got everything right.
https://github.com/gorhill/uBlock/blob/master/doc/benchmarks/mem-usage-overall-20141224.ods
- Wiki home
- About the Wiki documentation
- Permissions
- Privacy policy
- Info:
- The toolbar icon
- The popup user interface
- The context menu
-
Dashboard
- Settings pane
- Filter lists pane
- My filters pane
- My rules pane
- Trusted sites pane
- Keyboard shortcuts
- The logger
- Element picker
- Element zapper
-
Blocking mode
- Very easy mode
- Easy mode (default)
- Medium mode (optimal for advanced users)
- Hard mode
- Nightmare mode
- Strict blocking
- Few words about re-design of uBO's user interface
- Reference answers to various topics seen in the wild
- Overview of uBlock's network filtering engine
- uBlock's blocking and protection effectiveness:
- uBlock's resource usage and efficiency:
- Memory footprint: what happens inside uBlock after installation
- uBlock vs. ABP: efficiency compared
- Counterpoint: Who cares about efficiency, I have 8 GB RAM and|or a quad core CPU
- Debunking "uBlock Origin is less efficient than Adguard" claims
- Myth: uBlock consumes over 80MB
- Myth: uBlock is just slightly less resource intensive than Adblock Plus
- Myth: uBlock consumes several or several dozen GB of RAM
- Various videos showing side by side comparison of the load speed of complex sites
- Own memory usage: benchmarks over time
- Contributed memory usage: benchmarks over time
- Can uBO crash a browser?
- Tools, tests
- Deploying uBlock Origin
- Proposal for integration/unit testing
- uBlock Origin Core (Node.js):
- Troubleshooting:
- Good external guides:
- Scientific papers