prehistoric-systems/uBlock
1
0
Fork 0
mirror of https://github.com/gorhill/uBlock.git synced 2026-03-11 09:04:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

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

Raymond Hill 2015-02-18 00:21:12 -05:00
parent 38ac7c1e17
commit f7d37225f3
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -20,10 +20,11 @@
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 than 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 <sup>[1]</sup>, 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.
<sub>[1] See <https://www.youtube.com/watch?v=BpypOeK10N8></sub>
***
Also, if you want to look at memory figures, aside the above notes regarding garbage collection, keep in mind: