Skip to content

Loading…

Performance improvement opportunities for hostname-based cosmetic filters #133

Closed
gorhill opened this Issue · 1 comment

2 participants

@gorhill

For hostname-based (or entity-based) cosmetic filters, there is no need to use the same data structure as generic cosmetic filters. Hostname-based cosmetic filters can have their own optimal data structure.

This should help further reduce memory/CPU footprint, unsure how noticeable the result though.

@ialexsilva

looks good :+1:

@gorhill gorhill added a commit that closed this issue
@gorhill gorhill this fixes #133 b4b148e
@gorhill gorhill closed this in b4b148e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.