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

Continous Perfomance Testing #205

Open
kzys opened this issue Feb 27, 2020 · 0 comments
Open

Continous Perfomance Testing #205

kzys opened this issue Feb 27, 2020 · 0 comments

Comments

@kzys
Copy link
Contributor

kzys commented Feb 27, 2020

We don't have a mechanism to catch performance regressions (such as #198).

We use BuildKite to test all PRs are correct, but we optimize its configuration for Frugality. We run multiple tests in parallel which allows us to use a single bare-metal instance to run all tests, but the performance numbers we can get from there would be fluctuating, based on other builds running on the same time.

pendo324 pushed a commit to pendo324/firecracker-go-sdk that referenced this issue Aug 27, 2024
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