Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Browsers
Web Extensions
uBlock Origin update thread
Message
<blockquote data-quote="ForgottenSeer 92963" data-source="post: 974130"><p>Obeserved some unexpected behaviour of uBlockOrigin (which was chromium related) and checked on Github. I noticed some "Something to address" and "bug" labels on Github for uBlockOrigin. So I walked through the changes posted in this thread and noticed there is a lot of performance related refactoring under the hood, some examples since 1.39</p><p></p><p>- Refactoring work in static network filtering engine (will increase uBlock first load time)</p><p>- Suggest network filter as best candidate by default</p><p>- Fix regression of isBlockImportant()</p><p>- Store domain= option into trie container's character buffer</p><p>- Store regex filter pattern into bidi-trie buffer</p><p>- Remove classes specialized in handling single-wildcarded patterns</p><p>- Fine-tune static network filtering engine code</p><p>- Make FilterJustOrigin derive from FilterOriginHitSet</p><p>- Improve dealing with ambiguity in regex-based-looking network filters</p><p>- Reject generic HTML block filters</p><p>- Simplify handling of valid HTML tags in i18n files</p><p>- Give precedence to negated types in case of ambiguity</p><p>- Ignore pointless trailling *^ in network filters</p><p></p><p>Does someone has a clue why MrGorhill is putting so much effort in optimization with ManifestV3 on the horizon or is it just coincidence?</p></blockquote><p></p>
[QUOTE="ForgottenSeer 92963, post: 974130"] Obeserved some unexpected behaviour of uBlockOrigin (which was chromium related) and checked on Github. I noticed some "Something to address" and "bug" labels on Github for uBlockOrigin. So I walked through the changes posted in this thread and noticed there is a lot of performance related refactoring under the hood, some examples since 1.39 - Refactoring work in static network filtering engine (will increase uBlock first load time) - Suggest network filter as best candidate by default - Fix regression of isBlockImportant() - Store domain= option into trie container's character buffer - Store regex filter pattern into bidi-trie buffer - Remove classes specialized in handling single-wildcarded patterns - Fine-tune static network filtering engine code - Make FilterJustOrigin derive from FilterOriginHitSet - Improve dealing with ambiguity in regex-based-looking network filters - Reject generic HTML block filters - Simplify handling of valid HTML tags in i18n files - Give precedence to negated types in case of ambiguity - Ignore pointless trailling *^ in network filters Does someone has a clue why MrGorhill is putting so much effort in optimization with ManifestV3 on the horizon or is it just coincidence? [/QUOTE]
Insert quotes…
Verification
Post reply
Top
