From 23a82975335b0a335166b5fdd91b00a7194c0f91 Mon Sep 17 00:00:00 2001 From: gorhill Date: Sat, 20 Dec 2014 21:57:10 -0800 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 --- ...tprint:-what-happens-inside-µBlock-after-installation.md | 6 +++++- 1 file changed, 5 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 2d24d6d..c8ad386 100644 --- a/Memory-footprint:-what-happens-inside-µBlock-after-installation.md +++ b/Memory-footprint:-what-happens-inside-µBlock-after-installation.md @@ -19,4 +19,8 @@ Now if you have reach the point where there is a valid µBlock selfie, this is w 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 noticeably smaller then 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 such case, in subsequent launches, µBlock will perform very efficiently. \ No newline at end of file +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 noticeable more efficiently than what you may have observed right after you installed it. + +*** + +Related: ["Notes on memory benchmarks, selfies"](https://github.com/gorhill/uBlock/wiki/Notes-on-memory-benchmarks,-selfies) \ No newline at end of file