Troubleshooting Scala Memory Leaks
Briefly

We can troubleshoot and investigate issues more effectively when we know the history of our product - recent changes, incidents, bug fixes, etc.
Identifying a memory leak was challenging for me, and there is no one-size-fits-all solution. So, I was trying different approaches and observing the outcome.
Fortunately, we found a common pitfall: creating a new HTTP client ( OkHttpClient) instance for each request.
OkHttp performs best when you create a single OkHttpClient instance and reuse it for all of your HTTP calls.
Read at Medium
[
add
]
[
|
|
]