Stat idea: peak tracking for resident/dirty/etc.
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.2k
- Forks
- 1.6k
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 13
Description
In cases where stats were grabbed during a quiescent period, it'd sometimes be handy to know what the world looked like when the heap was at its largest (not exactly captured just by the peaks, but at least it's something).
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. First clarify which resident, dirty, and related statistics should be tracked and how peak-state reporting should work; done means an agreed design and corresponding tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100