-
Notifications
You must be signed in to change notification settings - Fork 917
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
[DOC] Update 10 minutes to dask-cudf #4665
Comments
This issue has been labeled |
This issue has been labeled |
Closes rapidsai#4665 Closes rapidsai#4946 Closes rapidsai#10614 Closes rapidsai#11931
Update the introductory documentation to take account of current best practices. In particular, use `compute` judiciously on `dask-cuDF` objects, and explain why we are doing so. Closes #4665 Closes #4946 Closes #10614 Closes #11931 Authors: - Lawrence Mitchell (https://github.com/wence-) Approvers: - GALI PREM SAGAR (https://github.com/galipremsagar) - Ashwin Srinath (https://github.com/shwina) URL: #12114
Report improvements to documentation
Location of incorrect documentation
Link
Describe the problems or issues found in the documentation
10 minutes to dask-cudf
should be refreshed (in 0.14). Here are a couple of suggestions, but it would be good to read through and update content wherever applicable.df.compute()
which will not work with larger datasets (example).to_parquet
segment since we support GPU accelerated parquet writing.The text was updated successfully, but these errors were encountered: