The CreatorCon Call for Content is officially open! Get started here.

Troubleshoot client UI rendering performance

Mikael Karlsson
Kilo Sage

Hi.

Users without high performance computers are complaining about extremely slow loading of SOW and Catalog Builder.

Support cannot find anything wrong with the instance and we've compared MS Edge Chromium performance traces between sluggish experience and ok experience.

 

On the sluggish machines, when Edge profiler thinks the rendering is done the page hasn't even begun to render.

On my 32GB 12 core laptop the SOW homepage renders completely in about 6 seconds when refreshed and the profiler shows the same. But on the sluggish machines it will take around 20 seconds before the UI is shown even though the profiler recorded it as done after 6 seconds as well.

 

What should we look at next, any other analysis tool (windows) we can use to find the culprit?

1 REPLY 1

SatyakiBose
Mega Sage

Hello @Mikael Karlsson 

  • Have you tried disabling all browser extensions and plugins?
  • And has the browser been upgraded recently?
  • Have you tried checking in Incognito mode?

With one of my customers, I had seen that the company tried to push some policies in the browser, which made the browser perform like a dead horse. 

In addition to that, we are currently using an application called Aternity.

Some of the features of Aternity are:

  • Capture the start point and end point of an application

  • Can create custom triggers for browser and specific website - ex ServiceNow

  • However, Aternity cannot capture the performance of frames. Most of the ServiceNow applications & modules are rendered within frames.

So how this works is:

  1. When Aternity is configured, all the system in your organization will be linked to Aternity monitoring tool.
  2. Now when you face slowness or performance issues on your system and browser, you need to open an incident in ServiceNow.
  3. Based on the CI selected, Aternity API will be triggered at it will capture details from the system and other dependencies.
  4. Based on this you can tell, where and what exactly in your system could the slowness be. The result after diagnosis looks like this, with a score.

SatyakiBose_0-1677666391987.png