Skip to content

Compute Resource Statistics #2990

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

Closed
ammario opened this issue Jul 14, 2022 · 9 comments
Closed

Compute Resource Statistics #2990

ammario opened this issue Jul 14, 2022 · 9 comments

Comments

@ammario
Copy link
Member

ammario commented Jul 14, 2022

As a developer, I want to see my resource consumption at a glance. This makes the UI look cool and can alert me to sizing issues with my workspace. Thus, it's related to #2121 and #2988.

Screen Shot 2022-07-14 at 11 24 40 AM

Hopefully we can go beyond v1 and show special stats depending on environment detection. For example:

  • Show GPU when one is available
  • Break up CPU (user, sys, idle)
  • Break up virtual memory (total, used, free)
  • Show load average
@sharkymark
Copy link
Contributor

I want a mini HTOP widget @ammario Right now I use web terminal to do it.

@ammario
Copy link
Member Author

ammario commented Jul 14, 2022

haha yeah @mark-theshark... let's definitely not get caught up in the v1 design and shoot for something beautiful.

Screen Shot 2022-07-14 at 2 35 44 PM

@ketang
Copy link
Contributor

ketang commented Jul 14, 2022

Not to argue against something more webby, but we could launch an non-interactive "terminal" embedded in the workspace page that is just htop.

Is there an analogous CLI experience for this? Other than ssh + htop of course.

@ammario
Copy link
Member Author

ammario commented Jul 14, 2022

That would require the user has htop, which is not included by default distros. We would also have to do some janky text processing to separate the process list from the resource values. We would also lose support for Windows. And, the element would be inconsistent with the rest of our design.

@ketang
Copy link
Contributor

ketang commented Jul 14, 2022

Fair enough. At some point we will have to think about how to avoid limiting ourselves to the lowest common denominator, but now is not the time, and this is not the feature.

@ammario
Copy link
Member Author

ammario commented Aug 18, 2022

Closing in favor of #3480

@ammario ammario closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2022
@bpmct bpmct reopened this Dec 6, 2022
@bpmct
Copy link
Member

bpmct commented Dec 6, 2022

Reopening since we haven't settled on a way to do this yet.

@bpmct
Copy link
Member

bpmct commented Jan 30, 2023

In v1, we relied on metrics-server to get accurate utilization from pods. Since top is inaccurate inside containers, we might need to think about solutions.

@bpmct
Copy link
Member

bpmct commented Mar 28, 2023

Closing in favor of #3480. It seems like one form of agent metadata will be used for this.

@bpmct bpmct closed this as completed Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants