Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Kernel launch latency

Open
  • Is something wrong?
#32 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
performance

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.

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

Dominant language
C++
Stars
331
Forks
37
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ProjectPhysX/OpenCL-Benchmark

All issues in ProjectPhysX/OpenCL-Benchmark

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.