Async Thread Pool Best Practice #8562
Unanswered
JKomoroski
asked this question in
Q&A
Replies: 1 comment 2 replies
-
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a Dropwizard application which is largely IO bound, so I am planning to make use of
CompletableFuture.runAsync
andCompletableFuture.supplyAsync
to wrap some of that IO work and get things running concurrently. I've had some great success so far in my prototypes.The default behavior is to send that work to the common ForkJoinPool workers, but I see the option to pass an Executor if desired. Given that the common pool will vary based on the environment, I am looking for some advice on what a good default practice is in dropwizard.
The three options I see are
Does anyone have some production experience and advice to shed?
Java 11 & Java 17, Dropwizard 2.1 & Dropwizard 4 if it matters.
Beta Was this translation helpful? Give feedback.
All reactions