You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
pendo324
pushed a commit
to pendo324/firecracker-go-sdk
that referenced
this issue
Aug 27, 2024
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.
The text was updated successfully, but these errors were encountered: