TimeoutError: signal timed out
when using the map-reduce paradigm via the Send API even for low parallelization (k=20)
#2397
Unanswered
wallacelim
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When trying to implement the map-reduce pattern (with close reference to this guide), I found that increasing the parallelization factor (i.e., number of concurrent
Send
calls) to ~20 will seemingly always throw aTimeoutError: signal timed out
.To reproduce, simply run the example code in the guide linked above, except with the following line changed:
Things I've tried that made no difference
In my mind, 20 is a surprisingly low ceiling (was hoping for at least ~1000), and so I wanted to know if this is expected? Even better, I'd love to understand why.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions