<#4129 Moving from flyteplugins - Use dask cuda wo...
# flyte-github
a
#4129 Moving from flyteplugins - Use dask cuda worker when GPU resource > 0 Pull request opened by eapolinario TL;DR If a gpu has been specified in the dask plugin resource, assume we want to use
dask cuda worker
i.e. that dask-cuda is present on the specified image. Type ☑︎ Feature ☑︎ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description Currently we build an arg to submit to the container and inject values such as threads and memory from the limits specified in the resources object in the dask plugin object. Dask cuda gives us many built in gpu tools and all that is required is to ensure dask cuda is installed and then to start out workers with
dask-cuda-worker
. So, in order to accomodate, we simply check for gpu limits in the dask plugin resources and overwrite the first arg to
dask-cuda-worker
. flyteorg/flyte GitHub Actions: Build & Push Image GitHub Actions: Bump git tags GitHub Actions: Integration Test GitHub Actions: Unit Tests (flyteplugins) / Run Unit Test GitHub Actions: Lint (flyteplugins) / Run Lint GitHub Actions: Docker Build Images (flytepropeller) / build_docker ✅ 24 other checks have passed 24/30 successful checks