Benchmark publishing: reproducible, peer-reviewed, multi-machine

Open
  • Is something wrong?
#489 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
performance

Research direction

Start with the design decisions in adr/0006-benchmark-publishing.md, since the three checklist items depend on it. The performance tests are referenced but not named, so locate them in the repository first. Done means the ADR's publishing process is followed, the tests have been peer-reviewed, and results exist from machines other than the Apple M5 the maintainer has.

Written by the indexing model from the issue text.

Description

perf

See ADR-0006.

  • Publish benchmark results (ADR-0006)
  • Peer-review the performance tests
  • Run performance tests on machines other than Apple M5 (only an M5 is available to the maintainer today)
Dominant language
Java
Stars
3
Forks
2
Avg merge
9h 19m
Merged PRs (30d)
154

Getting set up

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 dfa1/vortex-java

All issues in dfa1/vortex-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.