Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

JFR profiling does not report heap usage #301

Open
ashwini-mnnit opened this issue Sep 26, 2024 · 3 comments
Open

JFR profiling does not report heap usage #301

ashwini-mnnit opened this issue Sep 26, 2024 · 3 comments

Comments

@ashwini-mnnit
Copy link

I am trying to look in to JVM profile but the JFR is not reporting Heap usage. Is there a flag enable that ?

image

@mikemccand
Copy link
Owner

Hmm that's odd -- this is where we ask java to enable JFR recording: https://github.com/mikemccand/luceneutil/blob/main/src/python/benchUtil.py#L1185

And we use these settings: https://github.com/mikemccand/luceneutil/blob/main/src/python/profiling.jfc which seems to be enabling object allocation tracking.

Maybe we are missing settings to turn on JFR heap tracking?

@rmuir
Copy link
Collaborator

rmuir commented Sep 27, 2024

maybe. the file that ships with the JDK has a LOT of stuff enabled. When creating the .jfc file for profiling tests (which I think this derived from at one point), I disabled everything except the bare minimum, but then lowered the interval to 1ms. the idea was to give more fine-grained data but still keep low overhead. https://github.com/apache/lucene/blob/main/gradle/testing/profiling.jfc

You can look at the file shipped with the JDK if you want to see defaults. Maybe its even a better start for long-running benchmark? But I'd be careful of BOTH setting low intervals AND enabling the kitchen sink?

@ashwini-mnnit
Copy link
Author

@rmuir , The config you shared does not help either. Is this related to JDK version ? I am using jdk21.

image

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants