I have seen IIQ UI running very slow after our upgrade to 8.4 P1. It was happening only in PROD and we never seen it in non-prod environment. Removing -XX:MaxGCPauseMillis=200 from the JVM setting resolved it for us.
It is a Java Virtual Machine (JVM) configuration flag. It sets the target maximum duration (in milliseconds) for a Garbage Collection (GC) “stop-the-world” pause, during which the JVM temporarily freezes application threads to clean up memory.
Did you recently upgrade the Tomcat version, or did you start experiencing this issue after the Tomcat upgrade?
There was a known issue in certain Tomcat 9 versions that caused performance slowness in Java-based applications. Please verify your current Tomcat version and check it against the official Tomcat website to determine whether it is one of the impacted versions.
If it is affected, consider upgrading to a stable and supported version.
How frequently this is happening. The screenshot you shared, the time doesnt look bad. if this is intermittent issue can it be narrowed down to one of UI node?
Also any recent change done to the IIQ deployment when you started seeing this issue?
Have you identified any pattern when the slowness occur? like happening with specific users/specific time/specific UI node?
Any other symptom seen like high GC, CPU saturation etc when this happens
Is it just home.jsf loading slow or others as well?
Is it slow for all users across all regions? Or specific user. If you are in GCP/AWS, check if users in the same zone or closer able to access properly or not.
the slowness could be isolated to specific UI servers, due to an unbalanced distribution of sessions by the Load Balancer. Please check that as well.
Do you have UI Servers act as Task Servers as well? If so, please try to segregate them. Have separate servers for UI and Tasks.
Also, check db performance, in case there are some heavy query being executed while you login.
If this is happening only for first time and better later so definitively caching is helping at later times.
Though I never faced this issue, check with your middleware team if they can enable compression so the load is faster even for first time. Also see if they can increase cache age as it seems its expiring daily.
Hi @pasha While upgrading from major version 8.2 to 8.3, we observed this issue. To overcome this, we applied patch p3. It worked in our case, try to upgrade from p2 to p3. I hope it will work.
For now we have changed server.xml to compress js files. This has improved the load time, especially for folks with slower internet speed.
These js files are just way too big and need to be broken up into smaller size bundles for specific pages. One js file to rule them all makes no sense.
