You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Load tests should be done before every DWO release.
Load tests should help us observe the controller's CPU and memory usage for 1000-1500 concurrent workspaces
Load tests should create automount configmaps and secrets to test its effect on memory usage
Exposed load tests via a make target (make test_load ...)
Run load tests in OpenShift CI after E2E tests
Added a step in .ci/openshift_e2e.sh to run load tests after E2E tests
The results from the CI OpenShift instance were inconclusive due to limited resources. Further investigation is needed to determine if we should run the tests with reduced load or on a different cluster.
Concurrency Tracking:
Noticed during a script-based investigation that the number of concurrently running DevWorkspaces was not matching the maximum number of VUs. Most DevWorkspaces were stuck in the Starting phase and were deleted as soon as they became Ready.
Added a configuration option to set a threshold for active workspaces, after which new DevWorkspaces will not be created.
Added an option to check if DevWorkspaces should be deleted at the end of each VU iteration.
With these new configuration options, we can now more accurately predict the number of DevWorkspaces created concurrently.
Pre-release Testing: Used these load tests for 3.23.0 pre-release testing on OpenShift instance provided by QE and documented the results.
Investigate Target Cluster: Investigate a target cluster to run these load tests before the release.
Cluster Bot (CPU exhaustion, preventing us from getting reliable performance results)
RH Demo Catalog (provides good cluster but has cost involved)
RH Resource Hub (CPU exhaustion, preventing us from getting reliable performance results)
Activity
rohanKanojia commentedon Sep 3, 2025
Load Test Implementation Progress
Here's a quick summary of the progress on this issue so far:
DevTools Week Investigation: Investigated tools for load testing.
Implement k6 Load Test PoC: Completed a proof-of-concept for k6 load tests (https://github.com/rohankanojia-testing/dwo-load-testing-using-k6-poc) with the following features:
k6binaryk6operatorMerge with Existing Scripts: Integrated the PoC with the existing Eclipse Che load test script (https://github.com/eclipse-che/che/blob/main/tests/performance/load-tests/load-test.sh).
logs/directoryIntegrate PoC into DevWorkspace Operator Code:
maketarget (make test_load ...).ci/openshift_e2e.shto run load tests after E2E testsConcurrency Tracking:
Startingphase and were deleted as soon as they becameReady.Pre-release Testing: Used these load tests for 3.23.0 pre-release testing on OpenShift instance provided by QE and documented the results.
Investigate Target Cluster: Investigate a target cluster to run these load tests before the release.