App Load Time

An important measure of user experience is the amount of time it takes for user mode applications to initialize fully before their user interface becomes accessible (clickable) by the user. Applications that are slow to load may indicate system issues, resource bottlenecks, and user frustration.

ControlUp has the ability to measure the time it takes any user-mode application to become available for the end user. This is an experimental feature that needs to be enabled and configured explicitly (for detailed instructions, see below). When configured, the application’s load time in seconds is displayed in the Processes view.

By default, the list of monitored applications includes Microsoft Office applications, Internet Explorer and Google Chrome.

In order to add an application for App Load Time monitoring, click on the Add Rule… button and provide the following parameters:

  • Process name/s, one per line - the name of the processes for which you would like to enable app load time monitoring. For every rule you create, it is recommended to enter process names that belong to a specific application or suite of applications, to enable for easier management of each application’s monitoring settings independently of other applications.

Note : The parameters below are advanced settings with recommended default values. It is not recommended to modify those values without thoroughly testing the effect of those changes on your production workloads.

  • First sample after (default: 20 s, accepted values: 2-180 s) - determines how long after the process is started will ControlUp first try to assess the load time of the application. For applications that are particularly slow to load, this parameter may be increased.
  • Threshold sensitivity (default: 7, accepted values: 2-12) - determines the sensitivity of the algorithm that detects a decline in the rate of activity generated by the process. You can try lowering this value if ControlUp fails to detect an application that appears fully loaded from the user’s perspective.
  • Stop measuring after (default: 180 s, accepted values: 2-180 s) - when this period elapses after the process start time, ControlUp will stop timing the process load duration. Set this value to the maximum duration that you would like to wait for the process to load. This setting also determines the maximum value you will see in the App Load Time metrics in ControlUp.
  • Data Sample Interval (default 20 ms, accepted values 5-20 ms) - determines the precision of the mechanism (lower = more precise) and its demand for CPU cycles (lower = more CPU activity).
  • Include I/O rate (default: enabled) - determines whether ControlUp should consider I/O activity when determining application load time. If unchecked, ControlUp uses only the DLL load rate.

 For application load time troubleshooting, please refer to this article - Application Load Time


1-on-1 Demo
Schedule now
Price Quote
Get it now
Need a Script?
Get it here
Powered by Zendesk