Enable external storage concurrency#2294
Merged
jmaeagle99 merged 4 commits intotemporalio:masterfrom Apr 16, 2026
Merged
Conversation
jmaeagle99
commented
Apr 15, 2026
jmaeagle99
commented
Apr 15, 2026
eamsden
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was changed
Allow worker external storage visiting to be concurrent by default with a default value of 3 max concurrent visits per workflow task. Client calls and activity tasks do not concurrently visit across their proto graphs as there is not much gain to do so.
Why?
With external storage being primarily I/O bound, a small amount of default concurrency should be enabled for workflow tasks so that uploads/downloads can process faster.
Checklist