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
select_ipc_gpu calls thrift api sql_execute_gdf and optionally calls deallocate_ipc_gpu, or the user should call deallocate_ipc_gpu.
select_ipc_gpu does not pass the device_id to deallocate_ipc_gpu, so sends 0 by default, but does not error if the memory is on device_id=1. Is this correct?
pyomnisci currently depends on pyarrow=3.0.0, but cudf uses 5.0.0. OmniSci may upgrade to 5.0.0 soon.
pyomnisci has this code @pytest.mark.skip(reason="deallocate non-functional in recent distros") from 3 years ago, so this should be re-enabled for testing.
Should select_ipc_gpu use numba.cuda.cudadrv.devices.gpus to implicitly select device for sql_execute_gdf and for the device onto which it inits the DataFrame?
The text was updated successfully, but these errors were encountered:
select_ipc_gpu
calls thrift apisql_execute_gdf
and optionally callsdeallocate_ipc_gpu
, or the user should calldeallocate_ipc_gpu
.select_ipc_gpu
does not pass thedevice_id
todeallocate_ipc_gpu
, so sends 0 by default, but does not error if the memory is ondevice_id=1
. Is this correct?pyomnisci currently depends on pyarrow=3.0.0, but cudf uses 5.0.0. OmniSci may upgrade to 5.0.0 soon.
pyomnisci has this code
@pytest.mark.skip(reason="deallocate non-functional in recent distros")
from 3 years ago, so this should be re-enabled for testing.Should
select_ipc_gpu
usenumba.cuda.cudadrv.devices.gpus
to implicitly select device forsql_execute_gdf
and for the device onto which it inits theDataFrame
?The text was updated successfully, but these errors were encountered: