Thanks Michael for the feedback!
I have asked to some Akka core dev and it seems that even if the tasks
aren't optimized for divide and conquer the
FJ pool is able to perform work-stealing without blocking under high
contention and high load, differently from the
Artemis pool that is backed by
+1 to investigate this for sure.
I’ve seen and attended a few of the same Akka presentations.
The main bit is for it to be able to split the work and execute in parallel
when possible (divide and conquer) so if the work/code isn’t splittable into
smaller units of concurrent work then not
HI guys!!!
after a couple of talks I've seen about Akka and the (seems good)
ForkJoinPool experience and a tons of metrics i have collected on Artemis
related to the current implementation used, I'm starting to believe that the
broker could benefit a lot by using a ForkJoinPool.
The current
