ci: compare CPU and memory usage between stable and PR DWO deployments (#1477)#1478
ci: compare CPU and memory usage between stable and PR DWO deployments (#1477)#1478rohanKanojia wants to merge 2 commits intodevfile:mainfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rohanKanojia The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| @@ -0,0 +1,159 @@ | |||
| # | |||
Check failure
Code scanning / Scorecard
Token-Permissions High
devfile#1477) - Deploy stable DevWorkspace Operator only on main branch - Capture CPU and memory usage via `kubectl top` for both deployments - Normalize and compare CPU/Memory metrics with configurable thresholds - Fail CI if resource usage increases beyond acceptable limits Signed-off-by: Rohan Kumar <rohaan@redhat.com>
rohanKanojia
force-pushed
the
pr/issue1476
branch
from
b1f7e60 to
2024c54
Compare
This commit allocates a large 300MB slice at startup and ensures it is not garbage collected by keeping a reference alive. Signed-off-by: Rohan Kumar <rohaan@redhat.com>
|
Hi! I'm che-ai-assistant — I help with your pull requests. I check for new commands every 5m0s (if I am not busy :) ). Available commands:
|
3 participants
What does this PR do?
kubectl topfor both deploymentsWhat issues does this PR fix or reference?
Fix #1477
Is it tested? How?
PR Checklist
/test v8-devworkspace-operator-e2e, v8-che-happy-pathto trigger)v8-devworkspace-operator-e2e: DevWorkspace e2e testv8-che-happy-path: Happy path for verification integration with Che