Interesting read...i'll test drive uBlock.
Pretty basic performance review between AdBlock Plus, uBlock and Bluhell:
http://ppcluddite.blogspot.ca/2015/02/a ... uhell.htmlI'll be testing for browser startup time, RAM usage on startup, and RAM usage with three tabs open (the three being IMDB, OS X Daily, and Gawker). The tests will be done on my Powerbook with TenFourFox 31 running a fresh profile with no other extensions. As a frame of reference, let's start out with no ad blocking:
startup time -- 8.5 seconds
RAM on startup -- 122 MB
RAM with three tabs open -- 265 MB
Those numbers are rough averages after a couple of run-throughs. Since the results were consistent, I didn't bother with more than two. Now let's get to Adblock Plus:
startup time -- 15 seconds
RAM on startup -- 200 MB
RAM with three tabs open -- 375 MB
The startup time includes about five seconds of a spinning beach ball while the ad blocker initializes. As you can see the memory went way up. Now let's see how uBlock does:
startup time -- 8.5 seconds
RAM on startup -- 165 MB
RAM with three tabs open -- 280 MB
No impact on startup time and modest bumps in memory usage. Finally, here's Bluhell Firewall:
startup time -- 8.5 seconds
RAM on startup -- 123 MB
RAM with three tabs open -- 215 MB
If memory is what you're going by, Bluhell is the clear winner. But does that mean it's the best? Its filters not being as extensive as Adblock Plus's, it lets the occasional ad through. It also lacks a whitelist feature, so you can't make exceptions for websites you want to support. Some people also report some site breakage.
In my opinion, uBlock is the more interesting alternative. It supports whitelists and is available on all major browsers. And as far as ad blocking goes, it's no slacker compared to Adblock Plus. In fact, Adblock Plus was overly aggressive, filtering out all of Gawker's "Promoted by..." posts. Most of those are embedded ads, but some are guest essays that, no matter how pretentious, should never be blocked.
I've always used NoScript combined with CSS rules based on floppymoose (the one shipped with Camino, to be exact) for ad blocking, but it's kind of a pain to edit your UserContent.css to include new rules for ads that get through. UBlock seems the more up-to-date option. In any event, NoScript should remain an essential item in your PowerPC toolbox to keep the Web loading fast and smooth while avoiding javascript catastrophes like this one, or this particular holocaust. I know there are a lot of about:config tweaks out there that promise big speed benefits (pipelining, etc), but they don't deliver much. To enhance the speed of your browser, it's really all about NoScript and a good ad blocker.
On my old hardware i can definitely concur with the review. Running Adblock Plus often brought my system to it's knees, while Bluhell helps the system run leaner than default due to less ads. Bluhell does leak some ads though but it's easy to install and doesn't require configuration. Most of my systems use NoScript and some without Flash, keeps them pretty lean.