hermit-os/uhyve

Investigate continuous benchmarking

Open

#1,043 opened on Aug 7, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (35 forks)auto 404
cienhancementfeature/optimizationhelp wanted

Repository metrics

Stars
 (293 stars)
PR merge metrics
 (PR metrics pending)

Description

See:

Over the past few months, various changes have been merged into Uhyve - those aim to improve configurability and security. At the same time, program paths have gotten much more complex.

To make the case for Uhyve's existence, keeping up with real-world benchmark numbers (as is done for the kernel itself: https://github.com/hermit-os/kernel/pull/1726) would be an interesting point to explore.

  • This repository already has a few benches that haven't "kept up with the times". They could be used to measure the project as a whole or individual components.
  • This repository could use images specifically intended for performance measurements.
    • Something simple like LINPACK or more complicated use cases (e.g. heavy hypercall usage over prolonged periods of time) could work.
  • See: https://github.com/hermit-os/hermit-bench

Contributor guide

Research direction
Examine existing benchmark files in the repository, identify outdated benchmarks, and design new performance measurement images (e.g., LINPACK) to enable continuous benchmarking. Integrate with the Hermit kernel's benchmark framework.
Tech stack
rust
Domain
backendperformancetesting
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustBenchmarking toolsDocker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55