You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In current setup, VDI, IDE and LaunchManager workloads can use GPU using the resource label nvidia.com/gpu. GPU instances are MIG-disabled by default. Robots should support MIG-enabled GPUs and different MIG instances. It can be done via labels like robolaunch.io/vdi-gpu-mig-instance.
Why is this needed?
It's needed to schedule computational and graphical processes to different GPU instances.
The text was updated successfully, but these errors were encountered:
What would you like to be added?
In current setup, VDI, IDE and LaunchManager workloads can use GPU using the resource label
nvidia.com/gpu
. GPU instances are MIG-disabled by default. Robots should support MIG-enabled GPUs and different MIG instances. It can be done via labels likerobolaunch.io/vdi-gpu-mig-instance
.Why is this needed?
It's needed to schedule computational and graphical processes to different GPU instances.
The text was updated successfully, but these errors were encountered: