Skip to content

Run 12616 gpu memory swap update #866

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Jul 22, 2024
Merged

Run 12616 gpu memory swap update #866

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8fd1da
RUN-12616 new known limitation added
JamieWeider72 Jul 16, 2024
2f893b9
RUN-12616 Added new known limitation
JamieWeider72 Jul 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/Researcher/scheduling/gpu-memory-swap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,6 +107,7 @@ If you prefer your workloads not to be swapped into CPU memory, you can specify

## Known Limitations

* A pod created before the GPU memory swap feature was eneabled in that cluster, cannot be scheduled to a swap-enabled node. A proper event is generated in case no matching node is found. Users must re-submit those pods to make them swap-enabled.
* GPU memory swap cannot be enabled if fairshare time-slicing or strict time-slicing is used, GPU memory swap can only be used with the default time-slicing mechanism.
* CPU RAM size cannot be decreased once GPU memory swap is enabled.

Expand Down
Loading