-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize greaselion startup performance #21366
Labels
Comments
atuchin-m
changed the title
Investigate performance impact of greaselion internal extensions
Optimize greaselion startup performance
Dec 28, 2023
The impact was investigated here: #33724 |
Closed in favor of #40873 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For some reason we create a lot internal extensions named
greaselion-xx
. It leads to allocate some structures for each of them.Moreover in may places chromium has linear search over all extensions therefore the number should be reasonable.
Therefore we suspect that have some noticeable performance impact.
The proposal:
1. measure the performance impact of these extensions2. merge all the extensions into the one(?) or find another way to optimize this.
The text was updated successfully, but these errors were encountered: