oneapi-src / oneapi-src/unified-memory-framework
check jemalloc perf in UR Compute Benchmarks - do we have a perf gap?
Open
Nobody has claimed this yet.
question
- Dominant language
- C
- Stars
- 98
- Forks
- 48
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 6
Description
check jemalloc perf in UR Compute Benchmarks
NOTE: the Disjoint Pool cannot be easily replaced by jemalloc (shared limits etc.), but we can easily check if we have a visible perf gap
Contributor guide
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 locating the UR Compute Benchmarks and identifying how the existing Disjoint Pool is measured. Compare its results with jemalloc where the benchmark permits, while accounting for the shared-limit constraint. Done means reporting whether a visible performance gap exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100