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
It was pointed out that logging spilling during evict() in Distributed using handle_errors provides useful information to users on spilling status. We don't currently provide a logger in Dask-CUDA (with a few exceptions where we capture Distributed's logger, which isn't a great solution), but it would be potentially useful to add similar logging to both DeviceHostFile and ProxifyHostFIle.
This issue has been labeled inactive-30d due to no recent activity in the past 30 days. 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 labeled inactive-90d if there is no activity in the next 60 days.
This issue has been labeled inactive-90d due to no recent activity in the past 90 days. 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.
It was pointed out that logging spilling during
evict()
in Distributed usinghandle_errors
provides useful information to users on spilling status. We don't currently provide a logger in Dask-CUDA (with a few exceptions where we capture Distributed's logger, which isn't a great solution), but it would be potentially useful to add similar logging to bothDeviceHostFile
andProxifyHostFIle
.cc @madsbk @shwina
The text was updated successfully, but these errors were encountered: