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 #273

Open
github-actions bot opened this issue Sep 21, 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

The test results from the last two days, specifically on 2024-07-31, show a substantial increase in both the Mean Kepler CPU Utilization and the Standard Deviation (Std Dev) percentages, indicating a significant performance regression.

Detailed Analysis:

  • On 2024-07-31 at 18:18:00Z, the Mean Kepler CPU Utilization was recorded at 0.3280331034%, which is a dramatic increase from the previous day's value of 0.0597766338% on 2024-07-30 at 18:15:51Z.
  • Similarly, the Std Dev on 2024-07-31 at 18:18:00Z increased to 0.2598348881% from 0.0362022150% on the previous day.
  • A second test on the same day (2024-07-31 at 19:50:43Z) also showed elevated levels with a Mean Kepler CPU Utilization of 0.3038928317% and a Std Dev of 0.2290510851%.

Conclusion:
The data from the last two days clearly indicates a significant performance regression based on the defined criteria of increases in CPU utilization and Std Dev. This suggests that changes made prior to the 2024-07-31 tests could be negatively impacting performance, warranting further investigation and potentially rolling back recent changes or optimizations.

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