mirror of https://github.com/gorhill/uBlock.git
Updated Notes on memory benchmarks, selfies (markdown)
parent
752a9bc51d
commit
b509308866
|
@ -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:
|
||||
|
Loading…
Reference in New Issue