séan35
Reputation: 1052
Managing ThreadPool and Connection Pool sizes with CompletableFuture for concurrent third-party API calls
I'm working on implementing concurrent third-party API calls for items in a list using CompletableFuture in Java. Instead of processing these requests sequentially, I want them to be executed asynchronously without waiting for each other.
We plan to use CompletableFuture, but I believe we'll need to manage the thread pool carefully. Without setting parameters like max pool size, the application might consume excessive memory and potentially freeze during high traffic.
My main concerns are:
- How should we determine appropriate thread pool and queue sizes for this scenario?
- We currently have a connection pool (size: 20) for third-party API calls. Should the thread pool size be limited to not exceed this connection pool size?
I'm specifically looking for:
- Best practices for sizing thread pools and queues in this scenario
- How to coordinate thread pool size with existing connection pool limitations
- Potential risks and mitigation strategies for memory management
Can anyone provide guidance on these aspects of concurrent API call implementation using CompletableFuture?
Upvotes: 1
Views: 61
Answers (0)
Related Questions
- What should be executor thread pool size while using Guava Rate limiter of 5 permits per second?
- Edited: Retrofit and CompletableFuture, is there a way to not rely on the underlying connection pool?
- why elasticsearch reject almost all queries when thread pool and queue is full instead of answering as much as possible and rejecting the remaining?
- How to execute non blocking HTTP calls in Java?
- Is it safe to have multiple Executors.newCachedThreadPool() in a Java program?
- How to understand "add up how much of that resource each task requires and divide that into the total quantity available" in deciding thread pool size
- What is the most performant way to setup multithreading using a choice of ThreadPool executor and Java7s CompletableFuture?
- How exactly does NodeJS handle high concurrent requests?
- Spring: Creating a truly scalable Thread Pool with ThreadPoolTaskExecutor