diff --git a/docs/source/deploying.rst b/docs/source/deploying.rst index 5df792b83ab..bfbee33602b 100644 --- a/docs/source/deploying.rst +++ b/docs/source/deploying.rst @@ -28,11 +28,13 @@ Deploy Dask Clusters An overview of cluster management with Dask distributed. -Single Machine --------------- +.. _deployment-single-machine: + +Local Machine +------------- -If you import Dask, set up a computation, and call ``compute``, then you -will use the the local threaded scheduler by default. +You don't need to do any setup to run Dask. In this case, it will use threads +in your local process. .. code-block:: python @@ -73,21 +75,6 @@ cluster managers, and so it's easy to swap out when you're ready to scale up. The following resources explain how to set up Dask on a variety of local and distributed hardware. -.. _deployment-single-machine: - -Single Machine --------------- - -Dask runs perfectly well on a single machine with or without a distributed scheduler. -But once you start using Dask in anger you’ll find a lot of benefit both in terms of scaling -and debugging by using the distributed scheduler. - -- :doc:`Default Scheduler ` - The no-setup default. Uses local threads or processes for larger-than-memory processing - -- :doc:`dask.distributed ` - The sophistication of the newer system on a single machine. This provides more advanced features while still requiring almost no setup. - Manual deployments (not recommended) ------------------------------------ diff --git a/docs/source/index.rst b/docs/source/index.rst index b76162d2a57..1607d1d3858 100644 --- a/docs/source/index.rst +++ b/docs/source/index.rst @@ -15,9 +15,9 @@ Dask .. grid-item:: :columns: 12 12 6 6 - + .. raw:: html - +
 
@@ -329,7 +329,7 @@ Learn more at :bdg-link-primary:`Deploy Documentation ` Coiled notably employs many of the active Dask maintainers today. - Learn more at :bdg-link-primary:`Coiled ` + Learn more at :bdg-link-primary:`Coiled ` - |saturn|_ provides Dask as part of their hosted platform including Jupyter and other products.