From 83153315c9842dedb6c9170d6d212ab13ce08f7b Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Fri, 13 Feb 2015 13:13:51 -0500 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 --- ...:-what-happens-inside-µBlock-after-installation.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md index 298657a..6f569a7 100644 --- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md +++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md @@ -1,12 +1,13 @@ 1. µBlock 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. **Five minutes later**, µBlock will look whether one or more filter lists need to be updated -1. If an update is needed, µBlock will flush from memory all filters and reload with the latest version + - 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 - 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 - - (You can disable auto-update if you want) -1. **Seven minutes later**, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock will make a selfie + - You can disable auto-update if you want, but it is optimal to let µBlock take care of this +1. **A few mintues minutes later**, assuming no change in selection of filter lists, or change in the content of selected filter lists, µBlock 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