Hacker News Reader

Ah, that's an interesting point, did not know that it could not use WebAssembly in Chrome yet (https://github.com/WebAssembly/content-security-policy/issue...). Would it be interesting to measure indeed, although the amount of wasm code there seems to be minimal so far.

View on HN

As far as I know WebAssembly in uBlock Origin is currently used for two things:

1. Matching the $domain option using an optimized Trie data-structure

2. Parsing domains using the public suffix list, also based on a Trie data-structure

I would love someone well-acquainted with the uBlock Origin code-base to update the benchmark so that we can compare.

Edit: All the code to create the dataset (as well as the dataset used for the study itself) and to run the benchmark and analyze the results (create the plots, etc.) is available on the repository and should be reasonably easy to run locally.

The same code used to match the `domain=` option is also used to match all filters which are essentially just a plain hostname, i.e. `||example.com^` -- which is a majority of filters found in filter lists.

afaik, in Chrome Web Assembly works fine when used inside Workers.

Reply on news.ycombinator.com