ProjectPhysX / ProjectPhysX/OpenCL-Benchmark
Kernel launch latency
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hi @ProjectPhysX,
Thank you very much for this benchmark. It's very concise, exactly what I was looking for.
A small suggestion here: what do you think about adding "kernel launch latency" as a new metric?
In our research it is of interest because we want to run CPU code then GPU code then CPU code and so on.
If you are interested in it we can discuss more.
Thank you again for the good work!
Regards
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
The issue names no files, tests, or entry points. Start by locating how the benchmark defines and reports its current metrics, then determine how CPU-to-GPU-to-CPU execution is represented; done means the benchmark reports kernel launch latency as a documented, reproducible metric.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100