Skip to content
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

CUDF gpu memory management #17

Open
mikehinchey opened this issue Oct 15, 2021 · 0 comments
Open

CUDF gpu memory management #17

mikehinchey opened this issue Oct 15, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request question Further information is requested

Comments

@mikehinchey
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant