Skip to content

[UX] Minor improvements of dstack metrics #2667

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

peterschmidt85
Copy link
Contributor

@peterschmidt85 peterschmidt85 commented May 20, 2025

  • Show run/job status
  • Better-format GPU metrics
  • Allow finished runs
  • Show GB (instead of MB)

Fixes #2316

* Show run/job status
* Better-format GPU metrics
* Allow finished runs
* Show GB (instead of MB)
@peterschmidt85 peterschmidt85 requested a review from jvstme May 20, 2025 09:31
Copy link
Collaborator

@jvstme jvstme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Show GB (instead of MB)

I don't think gigabyte granularity is enough.

  • It makes metrics useless for low-memory instances. Many clouds provide instances with only 1GB of RAM, some even provide 0.5GB RAM, including AWS. Such instances require precise memory consumption monitoring.
  • It makes it more difficult to see metric changes with dstack metrics -w. A metric can be growing or falling slowly but steady, which can be easily noticeable with megabyte, but not gigabyte granularity.

I suggest showing gigabytes with 2-3 digits after the decimal point, or reverting to megabyte granularity for both RAM and VRAM.

@peterschmidt85 peterschmidt85 requested a review from jvstme May 21, 2025 08:59
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

Successfully merging this pull request may close these issues.

[UX]: Active and finished jobs mixed in dstack stats
2 participants