From d80a00a54d54931a203720aefc00c3350f51186a Mon Sep 17 00:00:00 2001 From: gorhill Date: Tue, 9 Sep 2014 09:24:24 -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 d8fef63..2ed1021 100644 --- a/Notes-on-memory-benchmarks,-selfies.md +++ b/Notes on memory benchmarks, selfies.md @@ -6,7 +6,7 @@ However there are specific operations which will cause µBlock to churn through So in essence you won't obtain the same memory figures which I used in my published benchmarks if you caused µBlock to go through memory-churning before looking at the memory figures. -Reloading all the filters is quite a memory-churning operation. Here are operations which causes all the filters to be reloaded: +Reloading all the filters is the most severe memory-churning operation in µBlock. Here are operations which causes all the filters to be reloaded: - Launching or restarting µBlock (obviously). - Changing the selection of filter lists.