I always enjoy speaking to knowledgeable Cisco TAC engineers. I recently was experiencing some VERY SLOW WCS server response. The TAC engineer enlightened me to a “Server Diagnostics Page”
“I find it most successful to have multiple windows open to WCS at the same time, one of the GUI and one of the diagnostic page. Navigate a page in the GUI, then change windows to the diag page and click Refresh. Use the browser's File > Save As utility to capture a copy of the diag page while WCS is in pain, and send it in for review. We'll take a look at what the Java threads are doing, and what tables they're interacting with, and know better what actions to take to address the latency.” --TAC
https://<WCS>/webacs/pages/admin/serverDiagnosticInfo.jsp
