[Issue]: Fix load benchmark
Open
Nobody has claimed this yet.
benchmarks
bug
iris
- Dominant language
- Python
- Stars
- 202
- Forks
- 47
- Avg merge
- 6d 11h
- Merged PRs (30d)
- 4
Description
Problem Description
The load/store benchmarks need cache modifiers to accurately measure the HBM bandwidth. Some number are higher than peak (5563 GB/s) because of cache.
Operating System
Amy
CPU
Amy
GPU
Amy
ROCm Version
Amy
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response
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 load/store benchmark entry points and reviewing how their memory accesses are measured. Determine where cache modifiers belong so the benchmarks measure HBM bandwidth rather than cached data, then verify that results do not exceed the stated 5563 GB/s peak.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100