
9/30/2021 · Vladimir Zhuk
What this post added
This post details the use of Datadog's Continuous Profiler to identify a performance bottleneck in an Akka application. The issue was traced to the `ForkJoinPool` within the default Akka dispatcher, which was consuming significant CPU due to frequent thread parking and unparking caused by an irregular flow of tasks from the `LatencyReportActor`. The solution involved reconfiguring the `LatencyReportActor` to use a different dispatcher with a more stable task flow, resulting in a 30% drop in overall CPU usage and a reduction in the default Akka dispatcher's thread pool size.