Mirrors/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2024-07-03 02:37:21 +02:00
Code Issues Releases Wiki Activity

URL update, grammar / rewording fixes

q1800 2022-04-12 19:46:15 -05:00
parent 019733617e
commit a81ea3ee4f
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Myth:-uBlock-is-just-slightly-less-resource-intensive-than-Adblock-Plus.md

@ -1,15 +1,15 @@
No: it is significantly less resource intensive than Adblock Plus ("ABP").
No: it is significantly less resource-intensive than Adblock Plus (ABP).
Sloppy benchmarks can lead to the myth that uBlock Origin (uBO) is just a tad less resource intensive than ABP.
Sloppy benchmarks can lead to the myth that uBlock Origin (uBO) is less resource-intensive than ABP.
Rigorous benchmarks demonstrate that uBO is significantly more efficient than ABP.
Examples of sloppiness:
- Using memory footprint figures **before** the browser's garbage collector kicks in
- Not taking measures to avoid tainting memory footprint with [Chromium bug 441500](https://code.google.com/p/chromium/issues/detail?id=441500)
- Using memory footprint figures while option pages for one of the extension are opened
- Not taking measures to avoid tainting memory footprint with [Chromium bug 441500](https://bugs.chromium.org/p/chromium/issues/detail?id=441500)
- Using memory footprint figures while option pages for one of the extensions are open
- Disregarding the [contributed memory footprint to web pages](./Contributed-memory-usage:-benchmarks-over-time)
- Comparing memory footprint after extensions have run for a significantly different amount of time
- Using memory footprint figures after one of the extension has performed a one-time resource-intensive task (updating filter lists, etc.)
- Not taking into account the amount of filters in both extensions
- Using memory footprint figures after one of the extensions has performed a one-time resource-intensive task (updating filter lists, etc.)
- Not taking into account the number of filters in both extensions