microsoft / microsoft/gctoolkit
Diary enhancement for gen-z
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 177
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Description
The Diary is a summary of the a GCLog. From the diary we should be able to ask questions such as which garbage collector produced the GC log. In support of this, at least 1 new field will need to be added to the Diary and new discovery code will need to be added to the Diarizer process.
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 reading the Diary and Diarizer components and how the GCLog summary is currently discovered. Identify the existing fields and discovery flow before deciding how the garbage collector should be represented. Done means the Diary exposes the collector information and the Diarizer discovers it from supported GC logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100