-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Give new workspaces more resources #11144
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
Comments
What alternatives were considered and discussed? Would ensure that the IDE has enough resources during that time be sufficient? |
I think this would be unfair to the other workspaces running in the node. I could even abuse that running tasks knowing that I have more CPU |
👋 @Furisto thank you for creating this issue. @aledbf and I tested this recently with gen47 and gen51, and observed the same trend. It's an existing/old problem, I think, generally encountered when workspaces (usually monorepos) try to run too much. We should talk more before scheduling this issue, I am going to move back to our inbox for now. For example, there may be other ways to solve this problem. Perhaps we could do a combination of things:
|
In an effort to keep the Inbox tidy and with only actionable work, I will close this in favour of #10861 as the desired outcome is similar. Feel free to reopen if you disagree. |
Is your feature request related to a problem? Please describe
The experience of opening a new workspaces can be painful because setup tasks are running. Users have to wait until they can start working because not enough resources are available to fulfill all requests.
Describe the behaviour you'd like
Give new workspaces a higher priority (maybe use the already existing Qos attribute) during resource distribution.
The text was updated successfully, but these errors were encountered: