From fa540d658e5b8ec762f2cdaac40375735b4804e1 Mon Sep 17 00:00:00 2001 From: SW1FT Date: Sun, 22 Mar 2015 11:34:25 +0000 Subject: [PATCH] =?UTF-8?q?Updated=20Memory=20footprint:=20what=20happens?= =?UTF-8?q?=20inside=20=C2=B5Block=20after=20installation=20(markdown)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...happens-inside-uBlock-after-installation.md | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) rename Memory-footprint:-what-happens-inside-µBlock-after-installation.md => Memory-footprint:-what-happens-inside-uBlock-after-installation.md (56%) diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-uBlock-after-installation.md similarity index 56% rename from Memory-footprint:-what-happens-inside-µBlock-after-installation.md rename to Memory-footprint:-what-happens-inside-uBlock-after-installation.md index 4689f1e..db1095a 100644 --- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md +++ b/Memory-footprint:-what-happens-inside-uBlock-after-installation.md @@ -1,28 +1,28 @@ -1. µBlock will load the default selection of filter lists: +1. uBlock will load the default selection of filter lists: - This causes short-term memory churning (loading/parsing/sorting/storing), which short-term memory will be garbage-collected eventually - - All this short-term memory churning causes µBlock's baseline memory footprint to grow further -1. **A few minutes later**, µBlock will look whether one or more filter lists need to be updated -1. If one or more filter lists need to be updated, µBlock will launch a background task which will fetch an updated version of whatever filter list is deemed obsolete -1. Once all filter lists are brought up to date, µBlock will flush from memory all filters and reload with the latest version + - All this short-term memory churning causes uBlock's baseline memory footprint to grow further +1. **A few minutes later**, uBlock will look whether one or more filter lists need to be updated +1. If one or more filter lists need to be updated, uBlock will launch a background task which will fetch an updated version of whatever filter list is deemed obsolete +1. Once all filter lists are brought up to date, uBlock will flush from memory all filters and reload with the latest version - This will causes another round of short-term memory churning, which short-term memory will be garbage-collected eventually - - Again, all this short term memory churning causes µBlock's baseline memory footprint to grow further + - Again, all this short term memory churning causes uBlock's baseline memory footprint to grow further - You can disable auto-update if you want, but it is optimal to let µBlock take care of this, i.e. manually forcing an update is sub-optimal -1. **A few minutes later**, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock will make a selfie +1. **A few minutes later**, assuming no change in selection of filter lists, or change in the content of selected filter lists, uBlock will make a selfie - A selfie allows µBlock to skip the parsing/sorting of data next time it loads - Generating the selfie also causes short-term memory churning, which short-term memory will be garbage-collected eventually - - Again, this short term memory churning causes µBlock's baseline memory footprint to grow further - - 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 -- once the garbage collector does its job. -1. µBlock's much smaller _contributed memory_ footprint to web pages is much smaller than that of ABP + - Again, this short term memory churning causes uBlock's baseline memory footprint to grow further + - Any change in the selection of filter lists, or change in the content of selected filter lists will invalidate uBlock's selfie +1. Even after the growth in memory baseline, uBlock's _own memory_ footprint is still quite smaller than that of Adblock Plus -- once the garbage collector does its job. +1. uBlock's much smaller _contributed memory_ footprint to web pages is much smaller than that of ABP - The contributed footprint to web pages is part of the memory footprint of the web pages themselves - 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 µBlock relative to ABP -- because µBlock **does not** inject thousands of CSS rules into pages and embedded frames. + - Though this measure is not readily visible, it's where you get the biggest bang for the buck with µBlock relative to ABP -- because uBlock **does not** inject thousands of CSS rules into pages and embedded frames. -Now if you have reached the point where there is a valid µBlock selfie, this is when µBlock will run the most efficiently. +Now if you have reached the point where there is a valid uBlock selfie, this is when µBlock will run the most efficiently. -The next time you launch µBlock and there is a valid selfie, the load time will be a fraction of the load time when no selfie is available [1], and µBlock's baseline memory footprint will be smaller than when µBlock launches without a selfie available. +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 [1], and uBlock's baseline memory footprint will be smaller than when uBlock launches without a selfie available. -So my point is that µBlock will perform best efficiency wise if you leave it time to optimize itself after installation: In subsequent launches, µBlock will perform more efficiently than what you may have observed right after you installed it. +So my point is that uBlock will perform best efficiency wise if you leave it time to optimize itself after installation: In subsequent launches, uBlock will perform more efficiently than what you may have observed right after you installed it. [1] See ***