committed > reserved when preallocating huge pages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- c
- Domain
- performance
Research direction
Start by reproducing the statistics with MIMALLOC_RESERVE_HUGE_OS_PAGES or mi_reserve_huge_os_pages* and compare the reserved and committed arena values with RSS. Read the statistics output and huge-page allocation behavior first. Done means the reported utilization is explainable and the amount held in free lists is available or clearly accounted for.
Written by the indexing model from the issue text.
Description
When preallocating huge pages, either by MIMALLOC_RESERVE_HUGE_OS_PAGES or using mi_reserve_huge_os_pages*, I get confusing stats with current version:
[2026-02-27T04:50:08.531440Z] subproc 0
[2026-02-27T04:50:08.531529Z] pages peak total current block total#
[2026-02-27T04:50:08.531570Z] touched : 0 0 0 ok
[2026-02-27T04:50:08.531594Z] pages : 61.7 Ki 5.7 Mi 51.4 Ki not all freed
[2026-02-27T04:50:08.531616Z] abandoned : 56.0 Ki 5.5 Mi 45.7 Ki not all freed
[2026-02-27T04:50:08.531638Z] reclaima : 173.3 Ki
[2026-02-27T04:50:08.531660Z] reclaimf : 4.7 Mi
[2026-02-27T04:50:08.531682Z] reabandon : 681.6 Ki
[2026-02-27T04:50:08.531704Z] waits : 1
[2026-02-27T04:50:08.531725Z] extended : 0
[2026-02-27T04:50:08.531747Z] retire : 0
[2026-02-27T04:50:08.531768Z] searches : 2.8 avg
[2026-02-27T04:50:08.531790Z]
[2026-02-27T04:50:08.531812Z] arenas peak total current block total#
[2026-02-27T04:50:08.531833Z] reserved : 21.0 GiB 21.0 GiB 21.0 GiB
[2026-02-27T04:50:08.531857Z] committed : 36.9 GiB 36.9 GiB 36.9 GiB
[2026-02-27T04:50:08.531881Z] reset : 0
[2026-02-27T04:50:08.531903Z] purged : 0
[2026-02-27T04:50:08.531924Z] arenas : 3
[2026-02-27T04:50:08.531946Z] rollback : 0
[2026-02-27T04:50:08.531967Z] mmaps : 45
[2026-02-27T04:50:08.531988Z] commits : 0
[2026-02-27T04:50:08.532010Z] resets : 0
[2026-02-27T04:50:08.532031Z] purges : 0
[2026-02-27T04:50:08.532053Z] guarded : 0
[2026-02-27T04:50:08.532089Z] heaps : 1 1 1
[2026-02-27T04:50:08.532111Z]
[2026-02-27T04:50:08.532133Z] process peak total current block total#
[2026-02-27T04:50:08.532154Z] threads : 180 180 180
[2026-02-27T04:50:08.532176Z] numa nodes: 2
[2026-02-27T04:50:08.532198Z] elapsed : 28488.945 s
[2026-02-27T04:50:08.532219Z] process : user: 1936261.244 s, system: 58167.626 s, faults: 0, peak rss: 3.4 GiB, peak commit: 36.9 GiB
[2026-02-27T04:50:08.532241Z]
This shows 39GB committed and 21GB reserved. I definitely not using any additional memory beside reserved 21GB, not 36 - 21 = 15GB otherwise my RSS would be much larger.
So how am I supposed to get real memory utilization from this? Knowing my program I think it's using 15GB but I can't prove it with code.
Another stat I would like to know is how much of memory is in free lists.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 1.2k
- Avg merge
- 18h 12m
- Merged PRs (30d)
- 20
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from microsoft/mimalloc
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Building mimalloc with `-Wundef` compiler flag logs many warnings on undefined macrosPossibly taken @vstinner claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/mimalloc#1506 · 5 comments ·
Maintainers usually reply within 1 day
-
stale
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/mimalloc#1113 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/mimalloc#886 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/mimalloc#368 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/mimalloc
Similar issues
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
389ds/389-ds-base#8157 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
coolsnowwolf/lede#14305 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days