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

[Docs] Workspaces RAM and CPU requirements #14612

Closed
l0rd opened this issue Sep 20, 2019 · 4 comments
Closed

[Docs] Workspaces RAM and CPU requirements #14612

l0rd opened this issue Sep 20, 2019 · 4 comments
Assignees
Labels
area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@l0rd
Copy link
Contributor

l0rd commented Sep 20, 2019

Is your enhancement related to a problem? Please describe.

Users don't know how much RAM and CPU a workspace will need. They don't know if a workspace will fail to start or not in their cluster because of the memory or cpu limits.

We pre-calculate the memory limits for the defaults stacks (e.g. for angular it's 2686Mi). But we haven't documented how to calculate these limit for a custom stack.

Describe the solution you'd like

Write a document (under Using developer workspaces -> Workspaces memory and CPU requirements) that should answer the following question:

  • Given a devfile, how much RAM the corresponding workspace will need (the memory limit)?
  • Given a existing k8s cluster resource quotas and limit ranges policies how can I figure out if my workspace will be scheduled or not?

Write a document (under Administration Guide -> Cluster memory and CPU requirements) that answer the following question:

  • Given a sample workspace, and a number of users that should be able to use the workspace concurrently, what should be the cluster capacity and the suggested suggested resource quotas and limit ranges?
@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. team/platform severity/P1 Has a major impact to usage or development of the system. labels Sep 20, 2019
@slemeur
Copy link
Contributor

slemeur commented Oct 3, 2019

Linking to downstream issue: https://issues.jboss.org/browse/CRW-228

@l0rd l0rd added this to the Backlog - Platform milestone Oct 10, 2019
@l0rd l0rd self-assigned this Oct 14, 2019
@l0rd l0rd modified the milestones: Backlog - Platform, 7.3.0 Oct 14, 2019
@rkratky rkratky added the area/doc Issues related to documentation label Oct 29, 2019
@nickboldt nickboldt modified the milestones: 7.3.0, 7.6.0 Dec 12, 2019
@nickboldt
Copy link
Contributor

@l0rd @rkratky is this something we might get done for Che 7.9 / CRW 2.1? I know at least one customer who's looking for guidance ...

@nickboldt nickboldt modified the milestones: 7.6.0, 7.9.0 Feb 7, 2020
@l0rd
Copy link
Contributor Author

l0rd commented Feb 17, 2020

@nickboldt @themr0c @rkratky I have created the doc, I will seek for some reviews by TLs (and of course yours as well) and then I will transform it in asciidoc and publish it. Anyway it should be definately ready for 2.1.

@themr0c
Copy link
Contributor

themr0c commented Mar 11, 2020

fixed by eclipse-che/che-docs#1107

@themr0c themr0c closed this as completed Mar 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

5 participants