Skip to content

Conversation

@pf0n
Copy link
Owner

@pf0n pf0n commented Aug 14, 2025

No description provided.

Copy link

@ysramakrishna ysramakrishna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks mostly good.
Left a few comments.
Sorry for the delay in getting to this.

"0 will allow back to back young collections to run during old " \
"collections.") \
\
product(uintx, ShenandoahObjectCountInterval, 0, \

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"JFR" somewhere in the name so it's clear.

I wouldn't use "0" to mean disabled, since the enabling or disabling is controlled separately by whether the event is enabled or disabled.

In any case, I suppose your plan is to get this value from the JFR event in the future, so may be this semantics can be ignored (i.e. kept) for now. I wouldn't spend time on it.

* & vm.opt.ExplicitGCInvokesConcurrent != false
* @library /test/lib /test/jdk
* @run main/othervm -XX:+UnlockExperimentalVMOptions -XX:+UseShenandoahGC -XX:+ExplicitGCInvokesConcurrent -XX:MarkSweepDeadRatio=0 -XX:-UseCompressedOops -XX:-UseCompressedClassPointers -XX:+IgnoreUnrecognizedVMOptions jdk.jfr.event.gc.objectcount.TestObjectCountEventWithShenandoah
* @run main/othervm -XX:+UnlockExperimentalVMOptions -XX:+UseShenandoahGC -XX:ShenandoahObjectCountInterval=300 -XX:+ExplicitGCInvokesConcurrent -XX:MarkSweepDeadRatio=0 -XX:-UseCompressedOops -XX:-UseCompressedClassPointers -XX:+IgnoreUnrecognizedVMOptions jdk.jfr.event.gc.objectcount.TestObjectCountEventWithShenandoah

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In order to get these events, you might need to sleep for a sufficient period of time so that the (non-gc) object count event is produced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants