From 97e05127e5c60d896079839257bd971c58e1cbe5 Mon Sep 17 00:00:00 2001 From: Mike Date: Sat, 17 Jan 2015 16:41:04 +0200 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 | 2 +- 1 file changed, 1 insertion(+), 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 c6e5ecd..b6276b6 100644 --- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md +++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md @@ -19,7 +19,7 @@ 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 then 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, 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.