doUIAction taking more time when invoked first time (v8.8.2)

Hi,

Greetings. Hope you are well! We recently upgraded to Pega 8.8.2 and CS 8.8.

Using a Web Mashup for NBAA Portal and noticed that when invoking search for a customer (first time), doUIAction activity is called which is taking more than 6 to 7 seconds, i see that it is loading scripts and stylesheets from disk cache (observed via Browser Dev Tools).

Is there any tuning which we can do so that doUIAction is performant?

It loads well with a second or 2 when searching for a customer next time whilst still in the portal, issue is only when doing it first time.

Any questions, please do let me know!

Regards,

Bharat

@KOMARINA The performance of the doUIAction activity can be influenced by various factors, including network latency, server performance, and client-side rendering. Since you mentioned that scripts and stylesheets are loaded from disk cache, it suggests that the initial load time might be due to the time it takes to fetch these resources. One approach to improve performance could be to ensure that these resources are minified and compressed to reduce their size. Additionally, you could look into implementing HTTP/2, which allows for faster loading of resources over a single connection. Also, ensure that your Pega platform and Customer Service application are properly tuned for performance. This includes optimizing database performance, properly configuring your application server, and ensuring that your Pega rules and data instances are optimized. If the issue persists, it might be beneficial to raise a support request with Pega for a more in-depth investigation.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Distorted UI Display in End User Logins (Basic Html UI Display)

uilding high performance Customer Service applications > User experienc

CSS styles loading arround 6MB in IE

System Takes Too Much Time To Display Search Results in an Auto Complete

@MarijeSchillern Thank you, we noticed that the requests are being redirected to a node that has lots of requests being processed, we segregated the traffic to a separate node tier within ocp.

Regards,

Bharat