microsoft / microsoft/mimalloc
Linux + mimalloc padding + NVidia driver: huge start-up times
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
Hello,
here's a trace of my app's startup (stopped at when the GUI shows up) with MI_PADDING: it takes roughly 5-6 seconds to show up
and without: (I highlighted the .init part which takes so much time above) ; it takes less than a second to startup in that case:
Everything else is fast, I wonder if it's something that could be fixed still ? My edit-compile-run cycle is around 2 seconds for development and it's nice to have as many safeties as possible but not at the cost of waiting 6 second between each code change :)
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 by reproducing the reported Linux startup traces with MI_PADDING enabled and disabled, using an NVIDIA driver as described in the issue. Compare the initialization delay and identify whether the allocator or driver interaction causes it; done means the cause is explained and a focused fix or confirmed limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100