From f7d37225f3f458dfcc834f123c4da80e5b2a0120 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Wed, 18 Feb 2015 00:21:12 -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 --- ...footprint:-what-happens-inside-µBlock-after-installation.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md index f0b3a3c..4689f1e 100644 --- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md +++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md @@ -20,10 +20,11 @@ Now if you have reached the point where there is a valid µBlock 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, and µBlock's baseline memory footprint will be smaller than when µBlock launches without a selfie available. +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. 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. +[1] See *** Also, if you want to look at memory figures, aside the above notes regarding garbage collection, keep in mind: