-
Notifications
You must be signed in to change notification settings - Fork 611
Don't setup managed memory if rmm isn't using default settings #6700
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
Don't setup managed memory if rmm isn't using default settings #6700
Conversation
csadorf
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just explicitly acknowledging the outcome from this thread: we should update our docs about our behavior when we can't enable UVM, otherwise good.
Previously `cuml.accel` would always install a new `ManagedMemoryResource` on for the current device when installed. We now only do this if rmm is using the default resource. If a user or library has already configured rmm, we continue using their settings. This lets `cuml.accel` compose better with `cudf.pandas`, since we won't clobber their memory resource setup after loading ours. Also added tests for the `cuml.accel` IPython magics, including tests loading `cudf.pandas` before and after `cuml.accel`.
37a97ed to
6981ec5
Compare
jcrist
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs are updated, ready for another review.
csadorf
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks a lot!
|
/merge |
|
I restarted the CI jobs. There was no outout in the failed build job, so not sure what went wrong but probably transient. |
viclafargue
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jcrist, LGTM
Previously
cuml.accelwould always install a newManagedMemoryResourceon the current device when installed. We now only do this if rmm is using the default resource. If a user or library has already configured rmm, we continue using their settings.This lets
cuml.accelcompose better withcudf.pandas, since we won't clobber their memory resource setup after loading ours.Also added tests for the
cuml.accelIPython magics, including tests loadingcudf.pandasbefore and aftercuml.accel.