Skip to content

Commit

Permalink
Merge pull request #57 from jacobtomlinson/gpu-docs
Browse files Browse the repository at this point in the history
Improve GPU documentation
  • Loading branch information
jakirkham committed Jan 29, 2020
2 parents 9a7e3d0 + 614f253 commit 46a228f
Showing 1 changed file with 10 additions and 4 deletions.
14 changes: 10 additions & 4 deletions doc/source/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -16,14 +16,14 @@ Pip
.. code-block:: console
$ pip install dask-cloudprovider
Conda
^^^^^

.. code-block:: console
$ conda install -c conda-forge dask-cloudprovider
-----

Below are the different modules for creating clusters on various cloud
Expand Down Expand Up @@ -73,9 +73,9 @@ will be created automatically like in ``FargateCluster``.
GPU Support
~~~~~~~~~~~

There is also support in ``ECSCLuster`` for GPU aware Dask clusters. To do
There is also support in ``ECSCluster`` for GPU aware Dask clusters. To do
this you need to create an ECS cluster with GPU capable instances (from the
``p3`` or ``p3dn`` families) and specify the number of GPUs each worker task
``g3``, ``p3`` or ``p3dn`` families) and specify the number of GPUs each worker task
should have.

.. code-block:: python
Expand All @@ -85,6 +85,12 @@ should have.
cluster_arn="arn:aws:ecs:<region>:<acctid>:cluster/<gpuclustername>",
worker_gpu=1)
By setting the ``worker_gpu`` option to something other than ``None`` will cause the cluster
to run ``dask-cuda-worker`` as the worker startup command. Setting this option will also change
the default Docker image to ``rapidsai/rapidsai:latest``, if you're using a custom image
you must ensure the NVIDIA CUDA toolkit is installed with a version that matches the host machine
along with ``dask-cuda``.

.. toctree::
:maxdepth: 3
:hidden:
Expand Down

0 comments on commit 46a228f

Please sign in to comment.