jtec / jtec/prx

Add benchmarking to CI

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
23
Forks
9
Avg merge
5d 12h
Merged PRs (30d)
4

Description

Running a benchmark on orbit and clock computations seems like a good start, as that is where prx spends most of its time right now.

We can use https://github.com/marketplace/actions/continuous-benchmark

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by locating the orbit and clock computation code and any existing benchmark or test entry points in prx. Review the continuous-benchmark GitHub Action, then add CI coverage for those computations and verify that benchmark results are produced during the workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, python
Domain
ci-cd
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.