Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Benchmark tests #97

Open
Mossaka opened this issue Apr 29, 2024 · 0 comments
Open

Benchmark tests #97

Mossaka opened this issue Apr 29, 2024 · 0 comments

Comments

@Mossaka
Copy link
Member

Mossaka commented Apr 29, 2024

While the integration test pipeline creates a k3d cluster for testing end-to-end workloads, we don't put any stress on the cluster to test the performance of the spin shim, and thus have no immediate response to performance degration of PR changes.

I propose to add a separate gh workflow to run some benchmark tests on the cluster:

  1. Load test: using tools like wrk or hey to load test the HTTP server and report result as job annotations
  2. Baseline comparison: run spin apps on runc shim vs. spin-shim
  3. Gradual test: gradually scale out the pods and monitor the cpu, memory, disk and network io usages.

Related: containerd/runwasi#97

Feel free to add ideas and thoughts on this topic! Any suggestion is welcome 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant