From 5aa4699847d8137c2aa7cafbf149bc07ea4c7de9 Mon Sep 17 00:00:00 2001 From: q1800 <95879668+q1800@users.noreply.github.com> Date: Sat, 12 Feb 2022 14:29:03 -0600 Subject: [PATCH] Implement uBO naming convention --- ...appens-inside-uBlock-after-installation.md | 34 +++++++++---------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/Memory-footprint:-what-happens-inside-uBlock-after-installation.md b/Memory-footprint:-what-happens-inside-uBlock-after-installation.md index 98f825c..d3edfb1 100644 --- a/Memory-footprint:-what-happens-inside-uBlock-after-installation.md +++ b/Memory-footprint:-what-happens-inside-uBlock-after-installation.md @@ -1,28 +1,28 @@ -1. uBlock will load the default selection of filter lists: +1. uBlock Origin (uBO) will load the default selection of filter lists: - This causes short-term memory churning (loading/parsing/sorting/storing); short-term memory will be garbage-collected eventually - - 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 needs 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 obsolete -1. Once all filter lists are brought up to date, uBlock will flush from memory all filters and reload them with the latest version + - All this short-term memory churning causes uBO's baseline memory footprint to grow further +1. **A few minutes later**, uBO will look whether one or more filter lists needs to be updated +1. If one or more filter lists need to be updated, uBO will launch a background task which will fetch an updated version of whatever filter list is obsolete +1. Once all filter lists are brought up to date, uBO will flush from memory all filters and reload them with the latest version - This will cause another round of short-term memory churning; short-term memory will be garbage-collected eventually - - 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 uBlock 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, uBlock will make a selfie - - A selfie allows uBlock to skip the parsing/sorting of data next time it loads + - Again, all this short-term memory churning causes uBO's baseline memory footprint to grow further + - You can disable auto-update if you want, but it is optimal to let uBO 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, uBO will make a selfie + - A selfie allows uBO to skip the parsing/sorting of data next time it loads - Generating the selfie also causes short-term memory churning; short-term memory will be garbage-collected eventually - - 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 a bit smaller than that of Adblock Plus (ABP) -- 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 + - Again, this short-term memory churning causes uBO'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 uBO's selfie +1. Even after the growth in memory baseline, uBO's _own memory_ footprint is still quite a bit smaller than that of Adblock Plus (ABP) -- once the garbage collector does its job +1. uBO'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 uBlock relative to ABP -- because uBlock **does not** inject thousands of CSS rules into pages and embedded frames (unlike ABP) + - Though this measure is not readily visible, it's where you get the biggest bang for the buck with uBO relative to ABP -- because uBO **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, uBlock will run the most efficiently. +Once you have reached the point where there is a valid uBO selfie, uBO 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 [1], and uBlock's baseline memory footprint will be smaller than when uBlock launches without a selfie available. +The next time you launch uBO and there is a valid selfie, the load time will be a fraction of the load time when no selfie is available [1], and uBO's baseline memory footprint will be smaller than when uBO launches without a selfie available. -So my point is that uBlock will perform at best efficiency if you give it time to optimize itself after installation: In subsequent launches, uBlock will perform more efficiently than what you may have observed immediately after you installed it. +So my point is that uBO will perform at best efficiency if you give it time to optimize itself after installation: In subsequent launches, uBO will perform more efficiently than what you may have observed immediately after you installed it. [1] See ***