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

Open
github-actions bot opened this issue Sep 12, 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:
Upon reviewing the test results from the last two days, a significant performance regression is observed in the Kepler CPU utilization metrics. Specifically, the test results from 2024-07-31 show a drastic increase in both the mean Kepler CPU Utilization and the Standard Deviation (Std Dev) percentages.

  1. Mean Kepler CPU Utilization:

    • On 2024-07-31 at 18:18:00Z, the mean CPU utilization jumped to 0.3280331034%, a substantial increase from the previous day's value of 0.0597766338% recorded at 2024-07-30T18:15:51Z.
    • A similar high value is observed in the subsequent test on the same day at 19:50:43Z, where the mean utilization was 0.3038928317%.
  2. Standard Deviation (Std Dev):

    • Alongside the mean utilization, the Std Dev also saw a significant rise. On 2024-07-31 at 18:18:00Z, the Std Dev was recorded at 0.2598348881%, compared to 0.0362022150% on the previous day.
    • The test at 19:50:43Z on 2024-07-31 also showed a high Std Dev of 0.2290510851%.

These metrics indicate a significant performance regression, as both the mean CPU utilization and the variability in CPU utilization (as indicated by Std Dev) have increased dramatically. This suggests that the system's performance under load has become less predictable and potentially less stable, warranting further investigation into the causes of this regression and potential mitigation strategies.

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