From fcd478fb0199205db731233d41c2bba517a20c83 Mon Sep 17 00:00:00 2001 From: gorhill Date: Tue, 9 Sep 2014 09:49:27 -0700 Subject: [PATCH] Updated Notes on memory benchmarks, selfies (markdown) --- ...hmarks, selfies.md => Notes-on-memory-benchmarks,-selfies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename Notes on memory benchmarks, selfies.md => Notes-on-memory-benchmarks,-selfies.md (92%) diff --git a/Notes on memory benchmarks, selfies.md b/Notes-on-memory-benchmarks,-selfies.md similarity index 92% rename from Notes on memory benchmarks, selfies.md rename to Notes-on-memory-benchmarks,-selfies.md index 017ceae..538b9fb 100644 --- a/Notes on memory benchmarks, selfies.md +++ b/Notes-on-memory-benchmarks,-selfies.md @@ -19,7 +19,7 @@ Reloading all the filters is the most severe memory-churning operation in µBloc Additionally, with version 0.6+, µBlock is able to create a selfie to improve its load time next time the browser is launched, and creating a selfie is also a memory-churning operation. However for this one particular operation, once the selfie is created, the reward is that subsequent launch of µBlock will become very efficient CPU- and memory-wise -- as all the downloading/parsing of filters from raw text files will be completely bypassed, causing µBlock to be fully loaded and ready in a fraction of the time it takes when no good selfie is available. -The time at which a selfie is created is at µBlock's discretion. Currently, this will happen some minutes after the filter lists has been loaded, so as to avoid launching memory-churning selfie creation operations before there is a good likelihood the user is done tampering with his selection of filters. +The time at which a selfie is created is at µBlock's discretion. Currently, this will happen some minutes after the filter lists have been loaded, so as to avoid launching memory-churning selfie creation operations before there is a good likelihood the user is done tampering with his selection of filters. Take note that all the benchmarks appearing on the main page are quite dated at this point, a lot of code has been added or changed in µBlock. So for version 0.6 I ran the reference benchmark to find out where µBlock stands memory efficiency-wise -- along with ABP 1.8.3 for comparison.