-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Performance test PVC with a single node saturated with workspaces #12744
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
It worked without issues. |
Thanks, @sagor999 ! Could you share
Sweet!! Could you share a link to the Grafana and some pictures for posterity? Just super excited, and am glad the test worked out well. 😁 |
Also, @sagor999 could you add this to our project and update the status? 🙏 |
Thanks, @sagor999 . It looks like when a node is saturated with PVC workspaces and has high R/W data, that system load also goes up (which is expected because we're not limiting I/O on each PVC). How is CPU usage when there's heavy disk R/W? Can you share a link to the Node Resource Usage for the above node from Grafana and attach a picture to this issue for posterity? It should still be present because it is from 11 days ago. Aside from the ☝ concern, I cannot think of anything else warranting keeping this issue open. Once you've got that in here, assuming you see no issue with CPU, please close the issue. However, if you do see an issue, please loop in @Furisto to help examine. |
@sagor999 is there anything left to do for stress testing individual nodes? |
I don't think so, plus individual PVCs should be less taxing on the system then massive RAID drives that we have currently. 🙏 (especially that we use software RAID) |
Okay, thank you @sagor999 ! Closing. 😁 |
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe
We should test how a node behaves when it is full of workspaces using PVCs, where there is disk activity in the workspaces.
Describe the behaviour you'd like
Questions
Additional context
We're not sure if the IO limiter is needed to cover these disks or not, and whether there will excessive CPU usage as a result of using PVCs for
/workspace
.The text was updated successfully, but these errors were encountered: