microsoft / microsoft/gctoolkit
StringDeduplication events should not be G1 specific
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 177
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Description
StringDeduplication events should not be G1 specific and be at least enabled for Shenandoah. I read they should be enabled for Serial GC, Parallel GC and ZGC as well but at least with Zulu17.28+13-CA this was not working.
java -XX:+UseStringDeduplication -XX:+UseParallelGC -XX:+PrintFlagsFinal -version | grep String
java -XX:+UseStringDeduplication -XX:+UseSerialGC -XX:+PrintFlagsFinal -version | grep String
java -XX:+UseStringDeduplication -XX:+UseShenandoahGC -XX:+PrintFlagsFinal -version | grep String
java -XX:+UseStringDeduplication -XX:+UseZGC -XX:+PrintFlagsFinal -version | grep String
Example file: shenandoah.log
Generated with:
-Xlog:gc*,stringdedup*=debug,gc+ref=debug,gc+age=trace,safepoint:file=shenandoah.log:time,level,tags
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the four Java commands in the issue and reviewing the provided shenandoah.log example. Then trace the GC log parser's handling of StringDeduplication events across collectors. Done means those events are no longer treated as G1-specific and the relevant collector outputs are handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100