-
Notifications
You must be signed in to change notification settings - Fork 82
Firefox version: benchmarking memory footprint
Note: Results have been updated with latest Firefox 41 and Chromium 45. The page is the same as the old one (Firefox 35/Chromium 39, archived here), except all figures have been updated using latest browser version.
Infamous VIM test: ABP 370 MB vs. uBlock 373 MB. Firefox 41 64-bit.
- 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 (+140 filters), extra malware domains (+1,487 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: 751.22 MB (reference memory usage)
- Adblock Plus 2.6.10: 639.49 MB (reference minus 111.7 MB)
- uBlock Origin 1.1.1: 465.86 MB (reference minus 285.4 MB, ABP minus 173.6 MB)
-
Chromium
- No blocker: 1,342.87 MB (reference memory usage)
- Adblock Plus 1.9.3: 1,525.4 MB (reference plus 182.5 MB)
- uBlock Origin 1.1.1: 1,110.02 MB (reference minus 232.9 MB, ABP minus 415.4 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 41.0 64-bit and Chromium 45.0.2454.85 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.
uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
- 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