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

Issues with GPU caching #61

Open
josiahsams opened this issue Jul 19, 2017 · 0 comments
Open

Issues with GPU caching #61

josiahsams opened this issue Jul 19, 2017 · 0 comments

Comments

@josiahsams
Copy link
Member

The following issues are identified on the Dataset APIs,

  1. Cached data should be passed on from one logical plan to another wherever the pointers referring to the columns fields are part of the RDDOUTPUT and not in GPUOUT. Cached GPUOUT fields will continue to be owned by the logical plan which invoke it.

  2. Unloading the GPU data should be possible only by the logical plan which owns it.

  3. Repetitive loadGpu calls on the same dataset should execute fast as data is already loaded into GPU from the first invocation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant