Push summary table from netperf to dependent project
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 61
- Forks
- 21
- Avg merge
- 26d 5h
- Merged PRs (30d)
- 1
Description
Today, quic.yml generates a README.md file containing a summary table for the results from all the perf tests.
However, the project (MsQuic) that triggered the test does not get any other information besides whether the performance test passed or failed.
We need to have a general system for projects like MsQuic, ebpf, xdp to get more information about performance test metrics.
This unblocks https://github.com/microsoft/netperf/issues/73
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
Start by reading quic.yml and the generated README.md summary table to understand how performance results are currently collected and published. Trace how dependent projects receive pass/fail status, then define a way for projects such as MsQuic, ebpf, and xdp to receive performance metrics; completion should unblock microsoft/netperf#73.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, networking, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100