-
Notifications
You must be signed in to change notification settings - Fork 94
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
Passing rmm_pool_size
larger than memory will not create a pool
#443
Comments
This should be fixed by dask/distributed#4297 . |
This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d. |
This is still an issue |
This issue has been labeled |
This issue has been labeled |
With dask/distributed#4297 merged in, this is now fixed:
|
During some conversations offline, I noticed passing
rmm_pool_size
that's larger than the total GPU memory will succeed, although no pool gets created or warnings get thrown. A simple reproducer is below:By checking
nvidia-smi
, it's clear that the cluster gets created but without a memory pool.The text was updated successfully, but these errors were encountered: