Issue with Batched Resolvers Executing Sequentially Instead of Concurrently
I have two batched resolvers here, for each element, I call the first, then the second.
the second however queues all it's execution, until all items have finished processing for the first, why?
https://effect.website/play#50008a15987d
observed:
- computing 1-10
- computing 11-20
- computing 21-30
- saving 1-10
- saving 11-20
- saving 21-30
expected:
- computing 1-10
- saving 1-10
- computing 11-20
- saving 11-20
- computing 21-30
- saving 21-30
the second however queues all it's execution, until all items have finished processing for the first, why?
https://effect.website/play#50008a15987d
observed:
- computing 1-10
- computing 11-20
- computing 21-30
- saving 1-10
- saving 11-20
- saving 21-30
expected:
- computing 1-10
- saving 1-10
- computing 11-20
- saving 11-20
- computing 21-30
- saving 21-30
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
