microsoft / microsoft/mimalloc
Optimal API Usage to Maximize Performance per Thread?
Open
Nobody has claimed this yet.
stale
- Dominant language
- C
- Stars
- 13.4k
- Forks
- 1.2k
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 13
Description
when there are no allocations or deallocations across threads (including single threaded programs), is there a way to avoid any kind of lock/synchronization penalty?
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 source file or test is named. Start by reviewing mimalloc's public allocation API and the synchronization behavior relevant to single-threaded and cross-thread use; a useful outcome would be a documented API recommendation or a clearly scoped change showing how to avoid unnecessary locking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100