Why was there a need to reduce allocations — was it a request from the business or an initiative of the team itself?

The need to reduce allocations arose as a team initiative based on analysis of application performance and resource consumption. A high level of allocations led to frequent garbage collector triggers, negatively impacting system latency and overall responsiveness.

We conducted profiling using tools such as pprof and identified hotspots where excessive memory allocation occurred. After code optimization, reducing the number of temporary objects, and using object pools, we were able to significantly decrease GC load.

This improved the stability and performance of the application, positively affecting user experience and reducing infrastructure costs.