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

Updated Memory footprint: what happens inside µBlock after installation (markdown)

Mike 2015-01-17 16:41:04 +02:00
parent b4db20bbae
commit 97e05127e5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Memory-footprint:-what-happens-inside-µBlock-after-installation.md

@ -19,7 +19,7 @@
Now if you have reached the point where there is a valid µBlock selfie, this is when µBlock will run the most efficiently.
The next time you launch µBlock and there is a valid selfie, the load time will be a fraction of the load time when no selfie is available, and µBlock's baseline memory footprint will be smaller then when µBlock launches without a selfie available.
The next time you launch µBlock and there is a valid selfie, the load time will be a fraction of the load time when no selfie is available, and µBlock's baseline memory footprint will be smaller than when µBlock launches without a selfie available.
So my point is that µBlock will perform best efficiency wise if you leave it time to optimize itself after installation: In subsequent launches, µBlock will perform more efficiently than what you may have observed right after you installed it.