adblock-tester VS adblocker

https://adblock-tester.com/ (source)

No well-known content blocker "process about 90,000 regexps" to find out whether a resource needs to be blocked or not, that's just not how it works internally.

Last time I ran benchmarks of all well-known content blockers using Ghostery's benchmark tool[1], all of them could process a network request under 20µs on average.

Some do have performance concerns, but it has nothing to do with network filtering, it has to do with other stuff they do beyond network filtering (for example see [2]) and declarativeNetRequest does not help there, so they will still suffer these performance issues under MV3.

---

[1] https://github.com/ghostery/adblocker/tree/master/packages/a...

[2] https://www.extremetech.com/computing/182428-ironic-iframes-...

Only benchmarking can tell, we shouldn't make assumption about this. Currently the only comparative benchmark which I know of is ghostery/adblocker and running it with the latest static filtering engines shows uBO performing better:

With that in mind, uBO's blocking engine is currently the fastest as demonstrated by latest Cliqz's benchmarks, so the "quicker" claim does not hold either.

Author of RSS Guard here. After considering many approaches, I managed to dump old C++-based slow adblocking mechanism from RSS Guard and replaced it with this.

Thanks to the Wexond Shield powered by Cliqz