prehistoric-systems/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2026-03-11 09:04:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

URL update, grammar/rewording fixes

q1800 2022-04-10 15:20:25 -05:00
parent c0c388d861
commit 1ae2a54053
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
Who-cares-about-efficiency,-I-have-8-GB-RAM-and|or-a-quad-core-CPU.md

@ -1,16 +1,16 @@
Doing more with less is a virtue in software. For users of uBlock Origin (uBO), this means:
- Less CPU churn when loading a web page, which may translate into noticeable faster page load.
- Higher memory consumption correlates with higher CPU-cycle consumption: whatever extra memory is used is memory which has to be allocated/written to/read from (at least once)/garbage collected.
- Less CPU churn when loading a web page may translate into a noticeable faster page load.
- Higher memory consumption correlates with higher CPU-cycle consumption. Any extra memory used is the same that needs allocated/written to/read from (at least once)/garbage collected.
- Free to use more filter lists:
- For instance, [ABP warns against using too many filter lists](https://adblockplus.org/en/getting_started#subscription): _"It is important to note that you should not add too many filterlists to Adblock Plus"_
- Longer battery life: each time unit, however small, in which the CPU is idle rather than churning translates into extended battery life.
- For instance, [ABP warns against using too many filter lists](https://adblockplus.org/en/getting_started#subscription): _"It is important to note that you should not add too many filter lists to Adblock Plus"_
- Longer battery life. Each time unit, however small, that the CPU is idle rather than churning translates into extended battery life.
- Free to use a blocker on less powerful devices
- For instance: [Reddit: _"ABP was a significant burden on my CPU"_](http://www.reddit.com/r/chromeos/comments/298jh1/just_a_tip_try_out_%C2%B5block_for_your_adblocking/)
- Free to add more useful features
- For instance: [Reddit: _"ABP was a significant burden on my CPU"_](https://www.reddit.com/r/chromeos/comments/298jh1/just_a_tip_try_out_%C2%B5block_for_your_adblocking/)
- Free to add more functional features
- Free to use more extensions
Memory and CPU cycles are finite resources. A sure way for a developer to **not** be hired when being interviewed is to dismiss efficiency work because "memory is plentiful" or "CPU nowadays are fast enough".
Memory and CPU cycles are finite resources. A sure way for a developer to **not** get hired when being interviewed is to dismiss efficiency work because "memory is plentiful" or "CPU nowadays are fast enough".
***
@ -20,9 +20,9 @@ _Wasting_ is not _using_.
***
Not convinced yet? Try using stopwatch to compare how fast web pages load when using one blocker compared to another.
Not convinced yet? Try using a stopwatch to compare how fast web pages load when using one blocker compared to another.
If you have a multi-core CPU, and hence plenty of spare CPU cycles, granted, there may not be such a noticeable difference in page load, but other popular blockers will definitely make use of plenty of whatever spare CPU cycles available (see below) to perform the same job as uBO.
If you have a multi-core CPU with plenty of spare CPU cycles, you may not notice a difference in page load. Other popular blockers will use any available CPU cycles (see below) to perform the same job as uBO.
CPU overhead<br>
![CPU overhead](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/benchmarks/cpu-usage-overall-chart-20141226.png)