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

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

In the test results from the last two days, there is a noticeable and significant increase in both the Mean Kepler CPU Utilization and the Standard Deviation (Std Dev) values, indicating a performance regression.

  1. Analysis of Recent Test Results:

    • 2024-07-31T18:18:00Z:
      • Mean Kepler CPU Utilization: 0.3280331034%
      • Std Dev: 0.2598348881%
    • 2024-07-31T19:50:43Z:
      • Mean Kepler CPU Utilization: 0.3038928317%
      • Std Dev: 0.2290510851%

    Compared to the previous results:

    • 2024-07-30T18:15:51Z:
      • Mean Kepler CPU Utilization: 0.0597766338%
      • Std Dev: 0.0362022150%
  2. Comparison and Conclusion:

    • The Mean Kepler CPU Utilization on 2024-07-31 shows an increase of approximately 0.268% and 0.244% at two different times compared to the previous day.
    • The Std Dev also shows a significant increase, indicating a higher variability and less stability in CPU utilization. The Std Dev increased by approximately 0.223% and 0.193% at two different times.

This substantial increase in both the mean utilization and variability suggests a performance regression. The changes are significant enough to warrant further investigation into the causes, which could include changes in test conditions, configuration, or external factors affecting the performance. Immediate attention and action may be required to address these regressions and return to the previous performance baseline.

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