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.

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

Add map task documentation #131

Merged
merged 1 commit into from
Mar 12, 2021
Merged

Add map task documentation #131

merged 1 commit into from
Mar 12, 2021

Conversation

katrogan
Copy link
Contributor

No description provided.

Signed-off-by: Katrina Rogan <[email protected]>
@katrogan katrogan force-pushed the map-task-documentation branch from 47b495d to a4aa6ba Compare March 12, 2021 00:14
A map task lets you run a task over a list of inputs within a single workflow node. This means you can run thousands
of instances of that task without creating a node for every instance, providing valuable performance gains. Furthermore
you can run map tasks on alternate execution back-ends, such as `AWS Batch <https://aws.amazon.com/batch/>`__ which is
a provisioned services that can scale to great sizes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have existing documentation on how to configure propeller to determine where to run an array task?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried searching for batch as I was writing this comment and couldn't find anything

@katrogan katrogan merged commit 131227e into master Mar 12, 2021
kumare3 pushed a commit that referenced this pull request Mar 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants