microsoft / microsoft/mimalloc
Determine peak heap usage when using mimalloc_reserve_os_memory
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
I'm testing the dev-slice branch and it seems to work really well when used in conjunction with `mimalloc_limit_os_alloc` and `mimalloc_reserve_os_memory` when you want to minimize page faults for predictable allocation workload. Nice work!
I'd like to find an optimal value for the `mimalloc_reserve_os_memory` option without having to perform trial-and-error. If I were to specify a large value for `mimalloc_reserve_os_memory` could I somehow determine the actual heap size used by my workload (e.g. via some runtime stat) so that I could then reduce the size of the `mimalloc_reserve_os_memory` to minimize RSS used by the process?
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 file or test is named in the issue. Investigate mimalloc_reserve_os_memory and the available runtime statistics, then define a way to measure the actual heap size used by a workload; done means the result can guide a smaller reservation without trial-and-error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100