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.

Sign up for GitHub

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

Jump to bottom

a few more small changes in conf docs #990

Merged
merged 6 commits into from Jun 12, 2019
Merged

a few more small changes in conf docs #990

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
5312fb3
a few more small changes in conf docs
danielskatz May 29, 2019
c4fa2a0
grammar fix
danielskatz May 29, 2019
e791ef8
Merge branch 'master' into danielskatz-patch-1
yadudoc May 30, 2019
099ef68
Merge branch 'master' into danielskatz-patch-1
benclifford May 31, 2019
36db85c
going back to configuration title
danielskatz Jun 12, 2019
8b37e6b
Merge branch 'master' into danielskatz-patch-1
benclifford Jun 12, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/userguide/configuring.rst
View file
Open in desktop
Expand Up @@ -5,13 +5,13 @@ Configuration

Parsl workflows are developed completely independently from their execution environment.
There are very many different execution environments in which Parsl programs and their apps can run, and
many of these environments have multiple options of how those programs and apps run, which makes
many of these environments have multiple options of how those Parsl programs and apps run, which makes
configuration somewhat complex, and also makes determining how to set up Parsl's configuration
for a particular set of choices fairly complex, though we think the actual configuration
itself is reasonable simple.

Parsl offers an extensible configuration model through which the execution environment and
communication with that environment is configured. Parsl is configured
communication within that environment is configured. Parsl is configured
danielskatz marked this conversation as resolved.
Show resolved Hide resolved
using :class:`~parsl.config.Config` object. For more information, see
the :class:`~parsl.config.Config` class documentation. The following shows how the
configuration can be specified.
Expand All @@ -34,7 +34,7 @@ configuration can be specified.
Please note that all configuration examples below require customization for your account,
allocation, Python environment, etc.

How-to Configure
How to Configure
----------------

The configuration provided to Parsl tells Parsl what resources to use to run the Parsl
Expand Down Expand Up @@ -110,8 +110,8 @@ In addition, examples for some specific configurations follow.
.. [*] We assume that each node has 32 workers. If there are fewer workers launched
per node, a higher number of nodes could be supported.

.. [*] 8000 nodes with 32 workers each totalling 256000 workers is the maximum scale that
we've tested the `ExtremeScaleExecutor` at.
.. [*] 8000 nodes with 32 workers each totalling 256000 workers is the maximum scale at which
we've tested the `ExtremeScaleExecutor`.

.. warning:: `IPyParallelExecutor` will be deprecated as of Parsl v0.8.0, with `HighThroughputExecutor`
as the recommended replacement.
Expand Down