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

Updated Memory footprint: what happens inside µBlock after installation (markdown)

gorhill 2014-12-20 21:48:34 -08:00
parent 2c7f17d6d5
commit e226a0f797
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
Memory-footprint:-what-happens-inside-µBlock-after-installation.md

@ -11,5 +11,6 @@
- Any change in the selection of filter lists, or change in the content of selected filter lists will invalidate µBlock's selfie
1. Even after the growth in memory baseline, µBlock's own memory footprint is still quite smaller than that of Adblock Plus.
1. µBlock's much smaller contributed memory footprint to web pages is much smaller than that of ABP
- As opposed to µBlock's own memory footprint, visible using Chromium's _"Task Manager"_, the contributed memory footprint cannot be seen by users
- Though this measure is not visible, it's where you get the biggest bang for the buck with µBlock relative to ABP -- because µBlock **does not** inject thousands of CSS rules into pages and embedded frames.
- The contributed footprint to web pages is part of the memory footprint of the web pages themselves
- As opposed to µBlock'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 µBlock relative to ABP -- because µBlock **does not** inject thousands of CSS rules into pages and embedded frames.