From b509308866671c2e94f053da832a6b60c554e896 Mon Sep 17 00:00:00 2001 From: gorhill Date: Tue, 9 Sep 2014 09:43: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 (93%) diff --git a/Notes-on-memory-benchmarks,-selfies.md b/Notes on memory benchmarks, selfies.md similarity index 93% rename from Notes-on-memory-benchmarks,-selfies.md rename to Notes on memory benchmarks, selfies.md index 3d1717e..2fc1951 100644 --- a/Notes-on-memory-benchmarks,-selfies.md +++ b/Notes on memory benchmarks, selfies.md @@ -8,7 +8,7 @@ However there are specific operations which will cause µBlock to churn through Memory-churning operations lead to a permanently higher memory baseline for µBlock, as can be seen in the browser's _Task Manager_. -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. +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, even after letting the browser's garbage collector do its job. Reloading all the filters is the most severe memory-churning operation in µBlock. Here are operations which causes all the filters to be reloaded: