If the IIQ server still feels sluggish even though everything looks normal on the surface, start by checking the JVM memory and garbage collection — long GC pauses or a full heap can quietly slow things down.
Next, take a look at the database performance; sometimes even a single slow query or missing index can make the whole system lag.
It’s also worth reviewing active threads and background tasks to see if any workflows or rules are stuck running in the background.
Keep an eye on the logs for signs of overloaded thread pools, heavy debug logging, or frequent cache resets that might be eating up performance.
Lastly, don’t forget to test the network connections between IIQ, the database, and other integrated systems — even small latency issues there can ripple through and make the UI feel slow.