Skip to content

Commit 75f9c5e

Browse files
committed
Adding GCE to executor docs
1 parent ad06b4b commit 75f9c5e

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docs/userguide/execution.rst

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,9 @@ Parsl currently supports the following executors:
8787
4. `parsl.executors.taskvine.TaskVineExecutor`: This executor uses `TaskVine <https://ccl.cse.nd.edu/software/taskvine/>`_ as the execution backend. TaskVine scales up to tens of thousands of cores and actively uses local storage on compute nodes to offer a diverse array of performance-oriented features, including: smart caching and sharing common large files between tasks and compute nodes, reliable execution of tasks, dynamic resource sizing, automatic Python environment detection and sharing.
8888
These executors cover a broad range of execution requirements. As with other Parsl components, there is a standard interface (ParslExecutor) that can be implemented to add support for other executors.
8989

90+
5. `parsl.executors.globus_compute.GlobusComputeExecutor`: This executor uses `Globus Compute <https://globus-compute.readthedocs.io/en/latest/index.html>`_
91+
as the execution backend to run functions on remote systems.
92+
9093
.. note::
9194
Refer to :ref:`configuration-section` for information on how to configure these executors.
9295

0 commit comments

Comments
 (0)