We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When investigating a page's performance related to allocations, I found that Primer::Classify was performing a significant number of allocations.
Primer::Classify
The places making the most allocations were:
Hash#except
We should try to measure, then reduce the number of allocations made in that class since it can be a hot path for primer components.
The text was updated successfully, but these errors were encountered:
@BlakeWilliams with #197 and #166
should we close this issue?
Sorry, something went wrong.
I think we're probably good to close this for now, but can probably write some follow-up issues to prevent regressions, catch new keys, refactor, etc.
Thanks for the reminder!
No branches or pull requests
When investigating a page's performance related to allocations, I found that
Primer::Classify
was performing a significant number of allocations.The places making the most allocations were:
Hash#except
We should try to measure, then reduce the number of allocations made in that class since it can be a hot path for primer components.
The text was updated successfully, but these errors were encountered: