From e285ccd72ddd0c7538787699518d27c7d91ce826 Mon Sep 17 00:00:00 2001 From: gorhill Date: Tue, 9 Sep 2014 09:49:01 -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 (94%) diff --git a/Notes-on-memory-benchmarks,-selfies.md b/Notes on memory benchmarks, selfies.md similarity index 94% rename from Notes-on-memory-benchmarks,-selfies.md rename to Notes on memory benchmarks, selfies.md index 62b2abb..017ceae 100644 --- a/Notes-on-memory-benchmarks,-selfies.md +++ b/Notes on memory benchmarks, selfies.md @@ -17,7 +17,7 @@ Reloading all the filters is the most severe memory-churning operation in µBloc - Adding removing custom filters. - Updating the filter lists (this may be done automatically if _Auto-update_ is enabled). -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. +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.