Loader failing if there are more items in queue than concurrency limit
See original GitHub issueWith 3 spritesheets and concurrency set to 2, some of the tests are failing. Please see the following fork:
https://github.com/tarling/resource-loader
Run npm run test
to run the slightly modified test
Will submit a PR if I can work out how to fix it
It seems quite similar to https://github.com/englercj/resource-loader/issues/7
Thanks
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why 'reservedConcurrency' isn't limiting the number of ...
I see, so the 'reservedConcurrency' does not control the number of lambdas running but will throw a ThrottlingException if an SQS event triggers ......
Read more >Lambda Concurrency Limits and SQS Triggers Don't Mix Well ...
Specifically, if you set the concurrency limit too low, Lambda can throttle due to taking too many messages off a busy queue. The...
Read more >Neptune Loader Command - AWS Documentation
Neptune supports queuing up as many as 64 loader jobs at a time. If an additional load request is submitted to the queue...
Read more >3 Pitfalls of AWS Step Functions and How You Can Avoid Them
If a batch has more than 40 items in, it splits the data into 40 more batches and recursively calls itself to fan...
Read more >Top 10 most common Java performance problems
The number of connections to your database controls how many concurrent queries can be executed against it. If there are too few connections...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for fixing this so quickly @englercj
Ok, so this happens because since the concurrency is saturated it can’t load the child resource that was added, as it is waiting for a concurrency slot to open. Since that child never loads, the parent never completes, and that slot never opens.
Maybe the solve here is to open the concurrency when it finishes loading and is running middleware.