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

Regression Detected in Kepler or kube-apiserver CPU Utilization Performance #275

Open
github-actions bot opened this issue Sep 23, 2024 · 0 comments

Comments

@github-actions
Copy link

Regression detected from the following reports:

Report: https://sustainable-computing-io.github.io/kepler-metal-ci/kepler-stress-test-metrics.html

Details:
Significant Regression Detected

Detailed Analysis and Conclusion:
The test results from the last two days, specifically on 2024-07-31, show a significant increase in both the Mean Kepler CPU Utilization and the Standard Deviation (Std Dev) compared to the previous days' results. Here are the specific figures:

  • On 2024-07-31 at 18:18:00Z:

    • Mean Kepler CPU Utilization: 0.3280331034% (previously around 0.06% on average)
    • Std Dev: 0.2598348881% (previously around 0.03% on average)
  • On 2024-07-31 at 19:50:43Z:

    • Mean Kepler CPU Utilization: 0.3038928317%
    • Std Dev: 0.2290510851%

These values represent a more than fivefold increase in CPU utilization and a nearly eightfold increase in variability (Std Dev), indicating a significant performance regression. This drastic change suggests potential issues in the system or test environment that need immediate investigation to identify the root cause and mitigate any negative impacts on system performance and stability.

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

0 participants