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

Open
github-actions bot opened this issue Sep 17, 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 specific 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%, a significant rise from the 0.0362022150% recorded on the previous day. This is an increase of approximately 617% in the variability of CPU utilization.

This sharp rise in both the mean utilization and variability indicates a performance regression, as defined by the significant increase in CPU utilization or Std Dev compared to the previous test results. The data points to potential issues that could be related to changes in the test environment, configuration, or other external factors affecting the performance on this specific date.

Further investigation into the changes made around this date or additional tests to confirm consistency of these results would be advisable to pinpoint the exact cause of the regression and to implement necessary fixes or adjustments.

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