Open kevink-sq opened 2 weeks ago
sendEvents should use sendThreadPool instead of the default ForkJoinPool.
sendThreadPool
ForkJoinPool
sendEvents uses the default ForkJoinPool via CompletableFuture.supplyAsync(runnable) which scales with the number of cpu.
CompletableFuture.supplyAsync(runnable)
See https://github.com/amplitude/Amplitude-Java/pull/107
cc: @izaaz
Expected Behavior
sendEvents should use
sendThreadPool
instead of the defaultForkJoinPool
.Current Behavior
sendEvents uses the default
ForkJoinPool
viaCompletableFuture.supplyAsync(runnable)
which scales with the number of cpu.Possible Solution
See https://github.com/amplitude/Amplitude-Java/pull/107