Updated Notes on memory benchmarks, selfies (markdown)

gorhill 2014-09-09 09:23:43 -07:00
parent 97eb326080
commit 2847d61bbf
1 changed files with 1 additions and 1 deletions

@ -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. 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 filters causes is quite a memory-churning operation. Here are operations which causes all the filters to be reloaded: Reloading all the filters is quite a memory-churning operation. Here are operations which causes all the filters to be reloaded:
- Launching or restarting µBlock (obviously). - Launching or restarting µBlock (obviously).
- Changing the selection of filter lists. - Changing the selection of filter lists.