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.

Sign up for GitHub

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

Jump to bottom

JFR feature causing excessive overhead when enabled #203

Closed
kford-newrelic opened this issue Jul 15, 2021 · 0 comments · Fixed by #204
Closed

JFR feature causing excessive overhead when enabled #203

kford-newrelic opened this issue Jul 15, 2021 · 0 comments · Fixed by #204
Assignees
@meiao
Labels
bug Something isn't working jfr

Comments

@kford-newrelic
Copy link
Contributor

With the 7.1.0 release (which enables the JFR feature by default), some customers have reported excessive agent overhead, in the form of:

  • Large object allocation counts
  • Increased memory utilization
  • Higher GC activity

Problem appears related to the JfrController thread

Internal tickets referring to the issue:
@kford-newrelic kford-newrelic added bug Something isn't working jfr labels Jul 15, 2021
@XiXiaPdx XiXiaPdx removed their assignment Jul 26, 2021
@meiao meiao mentioned this issue Aug 16, 2021
Draft
@meiao meiao linked a pull request Aug 18, 2021 that will close this issue
Performance improvements #204
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@meiao meiao

Labels
bug Something isn't working jfr
Projects
Java Engineering Board
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Performance improvements newrelic/newrelic-jfr-core
3 participants
@meiao @XiXiaPdx @kford-newrelic