Memory Leak issue on the API server
Case Study
Client assigned us a task to measure the performance of one of their API systems, as the client wanted us to find the bottleneck and help in fixing the issue.
We found everything was seamless while running the test, but we observed a performance issue during the long-duration test. During the investigation, we noticed that there were limited numbers of APIs available compared to our past project experience, but server stats showed extremely high resource utilization.
We worked on one of the projects and found that one response time on one page was very high. We started to drill down the UI and found that there is one API responsible for that page's 90% response time. Then we further started drill-down things and noticed that one custom object was leaking memory, which was the reason for higher resource consumption.
Everything goes smooth when the server starts, but after a couple of hours, everything starts getting slow because of the memory leak issue.
We drilled down and found the responsible object, which was the reason for this massive memory leak. While brainstorming with the architect team, we found that developers missed the basic coding practice, and because of that, objects were releasing the memory.
Softomate Solutions Limited
Deen Dayal Yadav
Online
