Skip to content
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

Rate limit jar collection processing #179

Closed
jack-berg opened this issue Jan 4, 2021 · 0 comments · Fixed by #183
Closed

Rate limit jar collection processing #179

jack-berg opened this issue Jan 4, 2021 · 0 comments · Fixed by #183
Assignees

Comments

@jack-berg
Copy link
Contributor

Jar collection processing can use high amounts of CPU at application startup. We should adjust the code to rate limit this process and effectively draw out jar processing over a longer period of time.

A rudimentary version of this strategy is available in this branch: https://github.com/newrelic/newrelic-java-agent/compare/rate-limit-jar-collector

Ideally the allowable rate would have a reasonable default, but also be configurable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant