-
Notifications
You must be signed in to change notification settings - Fork 161
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
[Feature] Support GPU blocks #1780
Comments
Closed
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant. |
peterschmidt85
changed the title
[Feature] Run multiple jobs concurrently on one instance with a fraction of resources GPU/RAM/disk
[Feature] Support GPU blocks
Nov 17, 2024
un-def
added a commit
that referenced
this issue
Dec 10, 2024
The shim is now able to process multiple tasks at a time. The global state for the existing "legacy" API is emulated. From the API caller's point of view, the shim works exactly the same as before. Part-of: #1780
un-def
added a commit
that referenced
this issue
Dec 10, 2024
The shim is now able to process multiple tasks at a time. The global state for the existing "legacy" API is emulated. From the API caller's point of view, the shim works exactly the same as before. Part-of: #1780
un-def
added a commit
that referenced
this issue
Dec 12, 2024
The shim is now able to process multiple tasks at a time. The global state for the existing "legacy" API is emulated. From the API caller's point of view, the shim works exactly the same as before. Part-of: #1780
un-def
added a commit
that referenced
this issue
Dec 13, 2024
* Collect GPU resource identifiers: UUIDs for NVIDIA, DRI render nodes for AMD * Request GPUs by identifiers when creating a container * Keep track of busy/idle GPUs * Move host-related code to a separate package * Don't `panic()` Part-of: #1780
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation and implementation notes: https://docs.google.com/document/d/1-0cInSwV3CkybQUi4w4KtsrkFw5grvYdKxGo0gqPh2w/edit?usp=sharing
The text was updated successfully, but these errors were encountered: