-
Notifications
You must be signed in to change notification settings - Fork 437
Manual update shouldn't take so much time on all browsers except Safari #998
Comments
It's worth noting, however, the sequential downloading itself has benefits across all browsers (a quick benchmark on Chrome 41 here reveals that uBlock's peak memory usage is 30% less if the updates are done sequentially vs. all at once). |
I have mentioned this to emphasize that there is no real deal breaker in reverting to the previous update mechanism on browsers other than Safari.
Right, that's nice, but isn't the 30% difference in memory drops down after a couple of garbage collections? Anyhow, even lowering the delay time to half of what is on Safari could gain some nice numbers in the memory compartment, and not to slow down by a high factor (depends on the number of the lists you have) the update mechanism on all other browsers. |
No. by design. if you end up flushing all caches and forcing an update all the time, this is really bad, you should not do so by respect for remote servers who host for free the filter lists. |
For the record, benefits of the current way:
|
After the change that has made to workaround a bug in Safari #978 ,
there is a wait time between each downloaded list, which I think should be lower or non existent to other browsers except of Safari.
Most of us don't have connection issues, and I think there is a possibility to lower this value for most of the users, except of the ones of Safari.
The text was updated successfully, but these errors were encountered: