microsoft / microsoft/mimalloc
question: mimalloc shows significant presense on cpu profiler graph
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
I am almost sure it's expected - it happens during a very active memory growth phase. Still, I would like to double-check that there is nothing that can be tuned in order to reduce the CPU usage of these routines. We are using v2.0.5
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
Start with the reported profiler graph and the memory-growth scenario described in the issue, using mimalloc v2.0.5 as the baseline. Profile the allocator routines during active growth and determine whether their CPU usage is expected or whether a tuning opportunity exists; done means documenting the finding and any supported adjustment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100