search

dask / dask-blog

Dask development blog
https://blog.dask.org/
30 stars 35 forks source link

Set scheduler GPU article back to draft state #165

Closed mrocklin closed 1 year ago

mrocklin commented 1 year ago

This conveys wrong information currently, which is causing some confusion.

cc @jacobtomlinson would you be ok with this as a short term solution?

netlify[bot] commented 1 year ago

Deploy Preview for dask-blog ready!

Name Link
Latest commit 0e8ed5d172e17ed2082573205d5d056f849f4324
Latest deploy log https://app.netlify.com/sites/dask-blog/deploys/6451261859283100083570d8
Deploy Preview https://deploy-preview-165--dask-blog.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

jacobtomlinson commented 1 year ago

I think this is a bit of an extreme move. It's not incorrect, this is our agreed best practice. Would prefer to soften up the language a little to make it clear that folks can go off-road.

mrocklin commented 1 year ago

this is our agreed best practice

I'm not sure that I agree with this. If someone wants to use PyTorch and Dask I think I wouldn't tell them "you need to have a GPU on your client and scheduler machines" I would probably point them to the pytorch example that works great from a mac.

This article says that the thing I think is best practice isn't possible. This article is wrong.

Would prefer to soften up the language a little to make it clear that folks can go off-road.

Sounds great. Is this something you have time to do or is this something that you're expecting me to do? My guess is that we're both busy. That's fine. While we're both busy, I propose that we unpublish the article that gives incorrect advice.

jacobtomlinson commented 1 year ago

Closing in favour of #166