Service Operations Workspace (SOW) - Slow Performance

[leec1]

We have recently deployed Service Operations Workspace with our Utah upgrade. At the same time turning on the New (Next exp) UI.  Since deployment we have received many escalations from our IT Service Desks that SOW performance is particularly bad in terms of response times and defects (See PRB1673239) . This situation continues  despite raising many related Hi cases and escalations to ServiceNow.  I can see there are many Problem records and general  fixes related to SOW  coming in Utah Patch 5 and 6.  Has anyone else experienced anything similar ? And if you have what actions are you condsidering or taken ? 

[ersureshbe]

Hi, the slowness reason many things are available.

if SOW customized not followed OOB then you should understand the custom script is creating an issue?

What type of browser is using? try to change the browser and test it

Not sure cache clear is following as per house keeping work. 

Try to restart the nodes if possible.

If nothing helps then option will be ServiceNow input and highlight the info what you tried and followed. 

[leec1]

Thanks Kilo, 

SOW is OOTB, no customizations. All browsers being used are up to date and we only use the ones recommended by ServiceNow. Clear cache  also being performed daily.

[Craig Reiter1]

We found that any internet filtering that may be in place at your organization can impact responsiveness of the Service Operations Workspace.

Also, a table that we found to be helpful was the Client Interaction (sys_client_interaction) table. The Network Time represents the round trip network duration, and it can be very helpful in finding possible delays on your side.

[rtimbro]

Craig -  we're having similar issues.  Just wondering what options were available to provide relief for the customer?  Appreciate any additional insight - thanks!