11–20 of 158 posts
The first plugin I install on a freshly installed system with Firefox is uBO. After that I harden the browser by changing stuff in about:config. Chrome has never been an option for us with privacy in focus. The guys behind uBO should get some price or something.
Earlier quoted context omitted.
Interestingly, my numbers are completely different relative to each other when compared with yours... I wonder how the number of runs is determined and if this affects the results. Benchmarking, the higher ops/sec the better. Firefox 63.0 on Fedora 64-bit. Test 100 needles against 16 dictionaries of hostnames - Set-based x 1,707 ops/sec ±1.93% (60 runs sampled) - Regex-based x 4,078 ops/sec ±0.88% (25 runs sampled) -…
That's what I got too: Benchmarking, the higher ops/sec the better. Firefox 63.0 on Linux 64-bit. Test 100 needles against 16 dictionaries of hostnames - Set-based x 1,992 ops/sec ±0.71% (15 runs sampled) - Regex-based x 5,148 ops/sec ±0.18% (30 runs sampled) - Trie-based (1st-gen) x 11,797 ops/sec ±0.49% (63 runs sampled) - Trie-based JS (2nd-gen) x 8,471 ops/sec ±0.50% (47 runs sampled) - Trie-based WASM (2nd-gen)…
Benchmarking, the higher ops/sec the better. Safari 12.0 on Apple iPhone (iOS 12.1).
Test 100 needles against 16 dictionaries of hostnames - Set-based x 3,763 ops/sec ±0.19% (68 runs sampled) - Regex-based x 392 ops/sec ±0.16% (66 runs sampled) - Trie-based (1st-gen) x 20,669 ops/sec ±0.15% (69 runs sampled) - Trie-based JS (2nd-gen) x 16,926 ops/sec ±0.71% (69 runs sampled) Done.
Earlier quoted context omitted.
they attached a benchmark, https://raw.githack.com/gorhill/uBlock/master/docs/tests/hns...
Results on mine: Benchmarking, the higher ops/sec the better. Firefox 63.0 on Windows 10 64-bit. Test 100 needles against 16 dictionaries of hostnames - Set-based x 1,443 ops/sec ±3.46% (54 runs sampled) - Regex-based x 4,093 ops/sec ±1.18% (25 runs sampled) - Trie-based (1st-gen) x 8,993 ops/sec ±1.92% (59 runs sampled) - Trie-based JS (2nd-gen) x 7,923 ops/sec ±2.81% (44 runs sampled) - Trie-based WASM (2nd-gen) x…
Benchmarking, the higher ops/sec the better.
Safari 12.0.1 on OS X 10.14.1.
Test 100 needles against 16 dictionaries of hostnames
- Set-based x 3,801 ops/sec ±1.01% (62 runs sampled)
- Regex-based x 370 ops/sec ±0.68% (60 runs sampled)
- Trie-based (1st-gen) x 15,679 ops/sec ±0.73% (63 runs sampled)
- Trie-based JS (2nd-gen) x 16,408 ops/sec ±2.50% (62 runs sampled)
Benchmarking, the higher ops/sec the better.
Firefox 63.0 on OS X 10.14.
Test 100 needles against 16 dictionaries of hostnames
- Set-based x 1,703 ops/sec ±3.46% (57 runs sampled)
- Regex-based x 4,210 ops/sec ±1.95% (26 runs sampled)
- Trie-based (1st-gen) x 9,961 ops/sec ±0.74% (65 runs sampled)
- Trie-based JS (2nd-gen) x 7,120 ops/sec ±0.61% (40 runs sampled)
- Trie-based WASM (2nd-gen) x 7,993 ops/sec ±0.81% (44 runs sampled)
Benchmarking, the higher ops/sec the better.
Chrome 70.0.3538.110 on OS X 10.14.1 64-bit.
Test 100 needles against 16 dictionaries of hostnames
- Set-based x 3,414 ops/sec ±5.66% (53 runs sampled)
- Regex-based x 4,667 ops/sec ±2.50% (28 runs sampled)
- Trie-based (1st-gen) x 10,665 ops/sec ±1.31% (56 runs sampled)
- Trie-based JS (2nd-gen) x 7,852 ops/sec ±1.66% (43 runs sampled)
- Trie-based WASM (2nd-gen) x 11,930 ops/sec ±2.49% (58 runs sampled)
Hardware:
MacBook Pro (15-inch, 2017)
Processor: 2.9 GHz Intel Core i7
Memory: 16 GB 2133 MHz LPDDR3
Graphics: Radeon Pro 560 4096 MB
Intel HD Graphics 630 1536 MB
I wish gorhill would make a Safari content-blocker version of ublock. None of the existing blockers (who mostly just package existing block lists and charge money for it..) work as well as uBlock IME.
Apple are basically neutering _all_ blockers, unfortunately. I don't know if they're planning on filling the void though.
The first plugin I install on a freshly installed system with Firefox is uBO. After that I harden the browser by changing stuff in about:config. Chrome has never been an option for us with privacy in focus. The guys behind uBO should get some price or something.
Earlier quoted context omitted.
That's what I got too: Benchmarking, the higher ops/sec the better. Firefox 63.0 on Linux 64-bit. Test 100 needles against 16 dictionaries of hostnames - Set-based x 1,992 ops/sec ±0.71% (15 runs sampled) - Regex-based x 5,148 ops/sec ±0.18% (30 runs sampled) - Trie-based (1st-gen) x 11,797 ops/sec ±0.49% (63 runs sampled) - Trie-based JS (2nd-gen) x 8,471 ops/sec ±0.50% (47 runs sampled) - Trie-based WASM (2nd-gen)…
Interesting that an iPhone XS is the fastest of all the benchmarks above. Benchmarking, the higher ops/sec the better. Safari 12.0 on Apple iPhone (iOS 12.1). Test 100 needles against 16 dictionaries of hostnames - Set-based x 3,763 ops/sec ±0.19% (68 runs sampled) - Regex-based x 392 ops/sec ±0.16% (66 runs sampled) - Trie-based (1st-gen) x 20,669 ops/sec ±0.15% (69 runs sampled) - Trie-based JS (2nd-gen) x 16,926 o…
The first plugin I install on a freshly installed system with Firefox is uBO. After that I harden the browser by changing stuff in about:config. Chrome has never been an option for us with privacy in focus. The guys behind uBO should get some price or something.
What sorts of things do you change in about:config?
Many stuff is disabled by default, but it’s a moving target. There are some tutorials online to read.
It depends on what the browser is used for. Some hardening breaks certain sites.
Some stuff to look at:
- dns-prefetch - geo - cookie - dom (disable, breaks sites) - browser.cache.disk - clipboard.events - media.peerconnection - healthreport - spoofRefererHeader
Chrome doesn’t remove history when closed is a big issue.
The first plugin I install on a freshly installed system with Firefox is uBO. After that I harden the browser by changing stuff in about:config. Chrome has never been an option for us with privacy in focus. The guys behind uBO should get some price or something.
You can (and should) give them money if you find value. Do it, feels good.