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

Open
github-actions bot opened this issue Sep 14, 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, indicating a 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 substantial increase from the previous day's value of 0.0597766338% recorded at 18:15:51Z.
  • Similarly, the Std Dev on 2024-07-31 at 18:18:00Z increased dramatically 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 of CPU utilization at 0.3038928317% and Std Dev at 0.2290510851%.

Conclusion:
The data from the last two days clearly indicates a performance regression based on the defined criteria of significant increases in CPU utilization and Std Dev. This suggests that there may be underlying issues in the system or recent changes that have adversely affected performance. Further investigation and analysis would be required to pinpoint the exact cause and to implement necessary fixes 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