News for hackers. Stuff that matters.
Re:µBlock for Firefox by molticrystal on Tuesday January 20, 2015 @05:20AM (#8916254)
How is the performance for the firefox port? I might of missed it, but all I see are reports in comparison to adblockers on chrome.
Re:µBlock for Firefox by msl09 on Tuesday January 20, 2015 @08:02AM (#8916699)
Re:µBlock for Firefox by zobzu on Tuesday January 20, 2015 @08:38AM (#8916837)
Wah Chromium uses way more ram than Firefox. 425M (firefox+ublock) vs 1.04G (chromium+ublock)

in all cases memory is reduced :)

Re:µBlock for Firefox by gorhill on Tuesday January 20, 2015 @09:11AM (#8916958)
I did warn on that page:

> You can't compare directly the figures between the browsers

Still, yes, Chromium uses more memory. A good part of this is because per-process tab. Once Firefox get the same per-process tab architecture, it will be easier to compare both browsers together.

Re:µBlock for Firefox by wooger on Tuesday January 20, 2015 @12:47PM (#8918187)
Yep, Chrome / Chromium are now the #1 reason to bump my ram to 16GB. While using a laptop for coding / VMs etc. I still find my browser eating more ram most of the time - it simply doesn't handle paging out gracefully, and is horrific for my uses with < 4GB ram on any OS.
Re:µBlock for Firefox by zobzu on Thursday January 22, 2015 @09:11PM (#8933070)
well, firefox seems set to use a process for UI and a process for all tabs (such as in nightly right now), the consumption is still far lower.
Re:µBlock for Firefox by exprL on Tuesday January 20, 2015 @08:41AM (#8916854)
I'd appreciate details of CPU consumption as well. Minute amounts of memory are of no concern for many people, but everyone prefers snappier browsing, every time.
Re:µBlock for Firefox by gorhill on Tuesday January 20, 2015 @10:47AM (#8917445)
Here: https://github.com/gorhill/uBlock#cpu

The details of the benchmark (if you want to reproduce) are in the spreadsheet linked in the caption.

Re:µBlock for Firefox by exprL on Tuesday January 20, 2015 @01:50PM (#8918659)
I was aware of the contents of the front page, having skimmed it again today (and read more carefully before, although with little interest for Chromium extensions). I'm only interested in performance characteristics in Firefox, but am unlikely to test this myself before it arrives in AMO.
Re:µBlock for Firefox by karon on Tuesday January 20, 2015 @11:00AM (#8917519)
How is that even possible? Firefox with blocker uses less RAM than without? Does it block elements from issuing requests?
Re:µBlock for Firefox by wtallis on Tuesday January 20, 2015 @12:17PM (#8917985)
One would expect any ad blocker that actually blocks ads to reduce memory consumption significantly. Ad blockers that merely hide ads exist and have succeeded in earning reputations as ad blockers despite only doing half the job.
Re:µBlock for Firefox by nnethercote on Tuesday January 20, 2015 @08:20PM (#8920913)
Alas, it's not that simple. See these bugs about AdBlock Plus's effects on Firefox's memory usage:

https://bugzilla.mozilla.org/show_bug.cgi?id=988266 https://bugzilla.mozilla.org/show_bug.cgi?id=1001426

Re:µBlock for Firefox by wtallis on Tuesday January 20, 2015 @10:05PM (#8921236)
That second bug is lacking in technical details, but the first one is clearly about the memory consumption of the CSS rules used to hide elements. If you only use rules that match URIs instead and not element ids, ABP is extremely efficient.

It's worth remembering that ABP only implemented the element-hiding feature so that things like inline text ads could be blocked, but now the popular rule lists are using a large number of broad rules to hide all kinds of elements, many of which could probably have been effectively blocked with URI-matching rules.

Additionally, it's very unfair to the ABP devs to be criticizing the performance or memory usage of ABP when the problem is really the memory usage of EasyList. Using a more restrained and targeted rule list makes the problems go away.

Re:µBlock for Firefox by scholia on Tuesday January 20, 2015 @07:29PM (#8920700)
True, but when I uninstalled Adblock Edge, I gained almost a gigabyte of memory in Firefox. (I'm now using Ghostery to block ads. It isn't as effective but I'd rather reduce the memory footprint.)