hyperlight-dev / hyperlight-dev/hyperlight-unikraft

Align benchmarks with hyperlight-core and the benchmarks repo

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

Nobody has claimed this yet.

Dominant language
Rust
Stars
24
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Benchmarks already exist. hluk bench runs cold, cold-snap, warm-restore, warm-stateful, and parallel modes; benchmarks/limits.json sets per-runtime, per-OS ceilings that gate CI; and results are charted per host OS via github-action-benchmark on gh-pages. The remaining work is deeper alignment with how hyperlight-core measures performance and with the shared benchmarks repo, so numbers are comparable across projects (methodology, metric names, and reporting).

Contributor guide

Open the contributing guide

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 with the existing hluk bench modes and benchmarks/limits.json, then compare their methodology and metric names with hyperlight-core and the shared benchmarks repo. Review how results are reported through github-action-benchmark on gh-pages. Done means the benchmark methods, names, ceilings, and reporting are aligned well enough for comparable cross-project numbers.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, rust
Domain
ci-cd, performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.