Add a working comparative GPU benchmark workflow/action
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Compare the steps around line 69 of .github/workflows/merge-tests.yml with the workflow discussed in lurk-lab/arecibo PR 238. Identify the common GPU benchmark pieces and determine how they can be exposed as a reusable workflow or action; done means another performance-focused repository such as grumpkin-msm can use it for comparative GPU benchmarks.
Written by the indexing model from the issue text.
Description
There is enough common ground between https://github.com/lurk-lab/lurk-rs/blob/main/.github/workflows/merge-tests.yml#L69 and https://github.com/lurk-lab/arecibo/pull/238 that we should be able to factor out some if not all steps into a reusable workflow or action.
This will help us extend GPU benchmarks to other performance-centric repos in the future like https://github.com/lurk-lab/grumpkin-msm
- Dominant language
- No language data
- Stars
- 0
- Forks
- 3
- Avg merge
- 10h 48m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from argumentcomputer/ci-workflows
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
argumentcomputer/ci-workflows#79 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
argumentcomputer/ci-workflows#49 ·
Maintainers usually reply within 1 day
-
Automate MSRV fixesOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
argumentcomputer/ci-workflows#42 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
argumentcomputer/ci-workflows#10 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
argumentcomputer/ci-workflows#8 · 1 comment ·
Maintainers usually reply within 1 day
All issues in argumentcomputer/ci-workflows
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ChicoState/autovalidate#195 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
elsa-workflows/elsa-core#8593 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MakerYuichi/Aegis-pro#114 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
jaseci-labs/jac#9744 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
objectionary/eo#9181 ·
Maintainers usually reply within 1 day