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
As it is, #8882 has added a scenario that breaks when GDS is configured. Currently GDS is disabled by default and we are not aware of anyone using it, but I am filing this to document that GDS will break in 23.10 unless we make some changes.
The least amount of change would be to have two "paths" for spilling buffers. Buffers/batches added to the device store could go to GDS, but if GDS is enabled a RapidsHostMemoryStore and a RapidsDiskStore would also be enabled and it would be available for host buffers and host batches. These "host originated" RapidsBuffer instances would only be able to go between host and disk, whereas the "device originated" RapidsBuffer instances would be allowed to go from RapidsDeviceMemoryStore to RapidsGDSStore, bypassing host memory/disk stores.
The text was updated successfully, but these errors were encountered:
As it is, #8882 has added a scenario that breaks when GDS is configured. Currently GDS is disabled by default and we are not aware of anyone using it, but I am filing this to document that GDS will break in 23.10 unless we make some changes.
The least amount of change would be to have two "paths" for spilling buffers. Buffers/batches added to the device store could go to GDS, but if GDS is enabled a
RapidsHostMemoryStore
and aRapidsDiskStore
would also be enabled and it would be available for host buffers and host batches. These "host originated"RapidsBuffer
instances would only be able to go between host and disk, whereas the "device originated"RapidsBuffer
instances would be allowed to go fromRapidsDeviceMemoryStore
toRapidsGDSStore
, bypassing host memory/disk stores.The text was updated successfully, but these errors were encountered: