"Carlos E. R." <robin.listas@telefonica.net> 08/14/15 8:43 AM >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-08-14 15:11, Christopher Myers wrote:
That sucks that Adblock Plus is a part of that, because I have that installed, and it's really nice :/
AddBlock uses lots of memory, because the stylesheet is loaded once per frame (FF bug). 4MB * N.
https://blog.mozilla.org/nnethercote/2014/05/14/adblock-pluss-effect-on-fire...
https://adblockplus.org/blog/on-the-adblock-plus-memory-consumption
http://www.reddit.com/r/programming/comments/25j41u/adblock_pluss_effect_on_...
Alternative: block some sites entirely (on hosts file), block scripts, block flash.
page with 400 iFrames, With ABP, needs 1960MiB http://vimcolorschemetest.googlecode.com/svn/html/index-c.html (Do NOT click!)
See this comment:
+++—-—-—-—-—-—-—-—- Chrome Dev here. We see this (and much more) with chrome as well.
Adblock, noscript, ghostery, and other addons like them cause 90% of the issues we see in the forums.
At the very least, by running any of these you are:
Increasing memory usage anywhere from 10% to 30% increasing overall cpu usage across all cores increasing overall load time of the page by about 15% to 50% completely screwing many of the optimizations that have gone into the browser, effectively making the multi-threaded nature of the browser fight itself.
This is because these programs need to interrupt any and all http calls to check them against a big list of "no-no" domains held in memory. If it matches, they remove the element from the dom so it doesn't load and let the browser continue.
This has the effect of making every single thread sync up each time the dom is updated, so these extensions can scan the new elements to ensure they aren't loading ads/scripts. Fancy stuff like threaded compositing, network predictors and prefetchers, and batched layout rendering are all abandoned when any one of these is in play. —-—-—-—-—-—-—-—-++-
Wow...that's crazy! And, would definitely explain some of the problems I've been having :/ At home, it's an easy fix for me because I run my own DNS servers, so I simply set up a bunch of ad zone files that point to a local apache install that has an .htaccess file that catches every URL posted to it and returns an empty page. -> problem solved :D Here at work (and in the wild) it's not quite so easy unfortunately. I could set up my hosts file to do that I guess, it would probably do the same thing in a lot of cases. I just found that the zone file + apache hack worked better because then I didn't get browser errors that way. Chris -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org