Performance Suite
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 39
- Forks
- 22
- Avg merge
- 10h 22m
- Merged PRs (30d)
- 3
Description
We need to work on adding a performance suite to testing. At minimum this should cover what's in:
And should test out different ways of structuring the EOSs, meaning things like using a variant, not using a variant, having every EOS be a table and one type, having inner loops where the type has been solidified, etc.
This should also test serial CPUs (looking for vectorization), OpenMP, CUDA, HIP.
When downstream users ask for recommendations, we can point them to this.
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 reading example/get_sound_speed_press.cpp and example/pte_2mat.cpp to identify the workloads the suite must cover. Define benchmarks comparing the listed EOS structures across serial CPU, OpenMP, CUDA, and HIP, including vectorization where applicable. Done means the suite covers these cases and provides recommendations for downstream users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100