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

[DOC] Update 10 minutes to dask-cudf #4665

Closed
ayushdg opened this issue Mar 23, 2020 · 3 comments · Fixed by #12114
Closed

[DOC] Update 10 minutes to dask-cudf #4665

ayushdg opened this issue Mar 23, 2020 · 3 comments · Fixed by #12114
Assignees
Labels
dask Dask issue doc Documentation Python Affects Python cuDF API.

Comments

@ayushdg
Copy link
Member

ayushdg commented Mar 23, 2020

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.
    • Reduce the number of examples that perform df.compute() which will not work with larger datasets (example).
    • Update to_parquet segment since we support GPU accelerated parquet writing.
@ayushdg ayushdg added doc Documentation Needs Triage Need team to review and classify labels Mar 23, 2020
@kkraus14 kkraus14 added Python Affects Python cuDF API. dask Dask issue and removed Needs Triage Need team to review and classify labels Mar 25, 2020
@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@GregoryKimball
Copy link
Contributor

Thanks @shwina for your changes in #10531, next time we dig into the docs for "10 Minutes to cuDF and Dask-cuDF", do you think these points are worth addressing?

wence- added a commit to wence-/cudf that referenced this issue Nov 10, 2022
@wence- wence- mentioned this issue Nov 10, 2022
3 tasks
@wence- wence- assigned wence- and unassigned shwina Nov 10, 2022
rapids-bot bot pushed a commit that referenced this issue Nov 28, 2022
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dask Dask issue doc Documentation Python Affects Python cuDF API.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants