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

µBlock -> uBlock

Carsten 2015-07-21 01:01:50 +02:00
parent 7ba2845831
commit d214d9651f
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Memory-footprint:-what-happens-inside-uBlock-after-installation.md

@ -18,7 +18,7 @@
- As opposed to an extension's own memory footprint, visible using Chromium's _"Task Manager"_, the contributed memory footprint to web pages cannot be easily seen by users
- Though this measure is not readily visible, it's where you get the biggest bang for the buck with uBlock relative to ABP -- because uBlock **does not** inject thousands of CSS rules into pages and embedded frames (unlike ABP)
Once you have reached the point where there is a valid uBlock selfie, µBlock will run the most efficiently.
Once you have reached the point where there is a valid uBlock selfie, uBlock will run the most efficiently.
The next time you launch uBlock and there is a valid selfie, the load time will be a fraction of the load time when no selfie is available <sup>[1]</sup>, and uBlock's baseline memory footprint will be smaller than when uBlock launches without a selfie available.