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

Open
github-actions bot opened this issue Sep 24, 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 significant increase in both the Mean Kepler CPU Utilization and the Standard Deviation (Std Dev) percentages. Here are the details:

  • On 2024-07-31 at 18:18:00Z, the Mean Kepler CPU Utilization was recorded at 0.3280331034%, which is a substantial increase from the previous day's value of 0.0597766338% recorded at 18:15:51Z. This represents an increase of approximately 448% in CPU utilization.
  • Additionally, the Std Dev on 2024-07-31 at 18:18:00Z was 0.2598348881%, up from 0.0362022150% on the previous day. This is an increase of over 617% in variability, indicating a less stable CPU performance.

This sharp rise in both CPU utilization and variability suggests a performance regression that could impact the stability and efficiency of the system under test. Further investigation into the causes of this regression is recommended to identify and mitigate any underlying issues.

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