Hello,
akka v2.6.19
scala 2.13.10
I have an akka system running that spawns an actor to serve the request. Inside the request actor it does cpu-computation work and make several non-blocking http requests. Previously, it uses the the default-dispatcher for all non-blocking http requests and for the request actor.
When I decided to separate out the request actor into it’s own dispatcher and other non-blocking http requests into it’s own dispatcher, it gave a better throughput, latency responses, and reduced timeouts from http requests. However, I noticed it increased the cpu-system utilization compared to a single default dispatcher approach. I’m not sure where and how the separation of dispatcher could increase the cpu-system utilization. Are there any thoughts as to what may be causing this increase or point me to a direction that would help with my investigation? Thanks.
1 post - 1 participant