From a81ea3ee4f8278f30b20cf1559b061d735275a95 Mon Sep 17 00:00:00 2001 From: q1800 <95879668+q1800@users.noreply.github.com> Date: Tue, 12 Apr 2022 19:46:15 -0500 Subject: [PATCH] URL update, grammar / rewording fixes --- ...htly-less-resource-intensive-than-Adblock-Plus.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Myth:-uBlock-is-just-slightly-less-resource-intensive-than-Adblock-Plus.md b/Myth:-uBlock-is-just-slightly-less-resource-intensive-than-Adblock-Plus.md index 9a93915..e2633ea 100644 --- a/Myth:-uBlock-is-just-slightly-less-resource-intensive-than-Adblock-Plus.md +++ b/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