test: start RealisticLoad after pod is Ready (real fix for contention)#51
Merged
Merged
Conversation
SebTardif
force-pushed
the
fix/realisticload-start-load-after-ready
branch
from
9f477f7 to
fd8892c
Compare
SebTardif
force-pushed
the
fix/realisticload-start-load-after-ready
branch
3 times, most recently
from
685b7f2 to
89d926d
Compare
Lower stress-ng pod requests from 300m/128Mi to 50m/32Mi so the pod schedules quickly on the contended k3d node (13 parallel E2E tests sharing ~4 CPUs). Burstable QoS lets the container burst to its actual ~200m CPU usage without affecting scheduling. Roll back the 3m readiness timeout (120s is sufficient) and the 6m recommendation poll timeout (3m is sufficient with fast scheduling). Fixes #49 Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
SebTardif
force-pushed
the
fix/realisticload-start-load-after-ready
branch
from
89d926d to
777e913
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lower stress-ng pod requests from 300m/128Mi to 50m/32Mi so the pod
schedules quickly on the contended k3d node (13 parallel E2E tests
sharing ~4 CPUs). Burstable QoS lets the container burst to its actual
~200m CPU usage without affecting scheduling.
Also lower MaxAllowed from 250m to 80m so the operator's max bound
is actually triggered (the recommendation of ~100m exceeds 80m),
preserving the BoundsApplied assertion.
Changes: