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

GPU/GRAM usage for workers and actors and nodes #13889

Closed
edoakes opened this issue Feb 3, 2021 · 2 comments · Fixed by #27074
Closed

GPU/GRAM usage for workers and actors and nodes #13889

edoakes opened this issue Feb 3, 2021 · 2 comments · Fixed by #27074
Labels
enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks

Comments

@edoakes
Copy link
Contributor

edoakes commented Feb 3, 2021

In the existing dashboard we can see both GPU usage and GRAM usage for workers.

@edoakes edoakes added enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks labels Feb 3, 2021
@edoakes edoakes added this to the New Dashboard Frontend milestone Feb 3, 2021
@hegdeashwin
Copy link
Contributor

@edoakes My Ray dev setup is on Apple Macbook Pro M1 (2020), which has 8 Core GPU. I trying running the Dev Ray with below command:

ray start --head --num-cpus=2 --num-gpus=1

But I'm not able to see the GPU column on Dashboard. What am I missing here.

@edoakes
Copy link
Contributor Author

edoakes commented May 10, 2021

Hey @hegdeashwin I responded on slack, but currently hte column only renders if you have a GPU installed in the cluster

Here is the relevant code that gets GPU usage:
https://github.com/ray-project/ray/blob/master/dashboard/modules/reporter/reporter_agent.py#L191

This will be returned in the proto to the frontend and it doesn't render the GPU column if nothing is returned. It might be nice to add something like a FAKE_GPU_USAGE env variable that would cause this to return some random numbers to test without actually having a GPU.

@alanwguo alanwguo changed the title GPU/GRAM usage for workers and actors GPU/GRAM usage for workers and actors and nodes May 31, 2022
rkooo567 pushed a commit that referenced this issue Aug 2, 2022
Support a GPU column for the new dashboard

Have first node be default expanded

Signed-off-by: Alan Guo [email protected]

fixes #13889

Addresses comment from #26996
alanwguo added a commit that referenced this issue Aug 2, 2022
Support a GPU column for the new dashboard

Have first node be default expanded

Signed-off-by: Alan Guo [email protected]

fixes #13889

Addresses comment from #26996
scv119 pushed a commit that referenced this issue Aug 3, 2022
Support a GPU column for the new dashboard

Have first node be default expanded

Signed-off-by: Alan Guo [email protected]

fixes #13889

Addresses comment from #26996
Stefan-1313 pushed a commit to Stefan-1313/ray_mod that referenced this issue Aug 18, 2022
Support a GPU column for the new dashboard

Have first node be default expanded

Signed-off-by: Alan Guo [email protected]

fixes ray-project#13889

Addresses comment from ray-project#26996

Signed-off-by: Stefan van der Kleij <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants