CHAPTeR 9 DXP PeRfORMANCe OPTIMIzATION • Common reasons: • Because of the nonscalable behavior (performance degradation with increase in user load) of the application, other applications are not able to support the projected volumes with this setup. • Recommendations: • Move the nonscalable application to a separate server. On a separate server this application was able to support the projected volumes. Alternatively transform the application to use microservice architecture and independently scale the microservices. • Do profiling of the nonscalable application to identify the root cause of the issue. • Deploy application, admin modules, and search modules on separate, individually scalable servers and containers. Performance Case study This section reviews a performance optimization case study for a DXP-based application. Application Context and Background The DXP application was built for a manufacturing organization. The DXP application provided web interfaces for suppliers, administrators, and distributors. During the user acceptance testing (UAT) testing, the team noticed performance issues on the landing pages for suppliers and distributors. The landing pages provided functionality to view the payments, processing, and transaction details for suppliers and distributors. The landing pages heavily used database queries to get the matching results. The landing pages were taking more than 120 seconds to load on various supported browsers. Performance Analysis Performance engineers applied the performance debugging framework we discussed earlier. Performance engineers analyzed the slow performing pages end to end to analyze all the layers and components involved in the web request processing pipeline. 254