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

Load test Che on real cluster #14629

Closed
rhopp opened this issue Sep 23, 2019 · 5 comments
Closed

Load test Che on real cluster #14629

rhopp opened this issue Sep 23, 2019 · 5 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current status/in-progress This issue has been taken by an engineer and is under active development.
Milestone

Comments

@rhopp
Copy link
Contributor

rhopp commented Sep 23, 2019

Target: 50-100 concurrent workspaces.
Descritpion TBD

@rhopp rhopp added kind/task Internal things, technical debt, and to-do tasks to be performed. team/che-qe labels Sep 23, 2019
@rhopp rhopp added this to the Backlog - QE milestone Sep 23, 2019
@ibuziuk ibuziuk added the severity/P1 Has a major impact to usage or development of the system. label Sep 23, 2019
@l0rd
Copy link
Contributor

l0rd commented Sep 24, 2019

cc @kameshsampath

@dmytro-ndp dmytro-ndp added the status/in-progress This issue has been taken by an engineer and is under active development. label Sep 25, 2019
@rhopp rhopp modified the milestones: Backlog - QE, 7.3.0 Oct 2, 2019
@Katka92
Copy link
Contributor

Katka92 commented Oct 15, 2019

I'm working on that issue for three weeks now. Currently, we can run load tests for multiple users. Each test is run with 1 user in 1 pod, using the same docker image as e2e tests with some changes (tests added, entrypoint changed). Results are sent to one specific pod via FTP and saved on PVC.
The test is written in typescript and is saved in e2e repo. This test starts workspace via factory URL and uses selenium to check that the workspace is started and IDE is loaded correctly. Currently, I'm facing problems with starting workspaces on OCP 4 with the FailedSchedulling error event and reaching limits.
TODO:

  • find appropriate memory/CPU limits for one test pod (for now seems like 700Mi memory and 400m CPU)
  • test logs processing part of tests (needs to have some passing tests)
  • consider having load tests as a separate image, differences to e2e image:
    • include FTP client
    • changed privileges for adding/changing files
    • a lot of logic added in entrypoint

@rhopp rhopp modified the milestones: 7.3.0, 7.4.0 Oct 16, 2019
@rhopp rhopp modified the milestones: 7.4.0, 7.6.0 Nov 28, 2019
This was referenced Dec 11, 2019
@Katka92
Copy link
Contributor

Katka92 commented Dec 18, 2019

The tests are done, PR with tests and README to show how to use it is merged. Closing.

@Katka92 Katka92 closed this as completed Dec 18, 2019
@l0rd
Copy link
Contributor

l0rd commented Jan 8, 2020

@rhopp @Katka92 we need to write down a document that help users to plan how many resources the wsmaster needs to support N concurrent workspaces. Is this something you can help with?

@slemeur
Copy link
Contributor

slemeur commented Jan 9, 2020

opened: #15641

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Development

No branches or pull requests

8 participants