Mirrors
/
uBlock
mirror of https://github.com/gorhill/uBlock.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Notes on memory benchmarks, selfies (markdown)

gorhill 2014-09-09 09:43:01 -07:00
parent 752a9bc51d
commit b509308866
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Notes-on-memory-benchmarks,-selfies.md → 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_. 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: Reloading all the filters is the most severe memory-churning operation in µBlock. Here are operations which causes all the filters to be reloaded: