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

feat: add missing MEM live stat of accelerators in session list #2801

Closed
yomybaby opened this issue Nov 1, 2024 · 1 comment · Fixed by #2802
Closed

feat: add missing MEM live stat of accelerators in session list #2801

yomybaby opened this issue Nov 1, 2024 · 1 comment · Fixed by #2802
Assignees

Comments

@yomybaby
Copy link
Member

yomybaby commented Nov 1, 2024

Currently, the session list only displays the Mem live stat information of CUDA. Please add the missing MEM live stat of other accelerators.
https://teams.microsoft.com/l/message/19:[email protected]/1730423621006?tenantId=13c6a44d-9b52-4b9e-aa34-0513ee7131f2&groupId=74ae2c4d-ec4d-4fdf-b2c2-f5041d1e8631&parentMessageId=1730271898438&teamName=devops&channelName=Frontend&createdTime=1730423621006

ironAiken2 added a commit that referenced this issue Nov 6, 2024
### This PR resolves #2801 Issue

Added memory usage monitoring capabilities for various accelerator types in the session list view. The following accelerators now display memory usage metrics with progress bars:

- TPU memory usage
- IPU memory usage
- ATOM memory usage
- ATOM+ memory usage and utilization
- Gaudi 2 memory usage
- Warboy memory usage
- RNGD memory usage
- LPU memory usage

Each accelerator type shows:
- Current/maximum memory usage in GiB
- Visual progress bar indicating memory utilization ratio
- Proper formatting of memory values without trailing zeros

**Checklist:**

- [x] Mention to the original issue
- [ ] Documentation
- [ ] Minium required manager version
- [ ] Specific setting for review
- [ ] Minimum requirements to check during review
- [ ] Test case(s) to demonstrate the difference of before/after
@ironAiken2
Copy link
Contributor

Resolved via #2802

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 a pull request may close this issue.

2 participants