---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Reviewing response time on forms

# Reviewing response time on forms {#ariaid-title1}

* Release version: Xanadu
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

A response time indicator (clock) appears at the end of many forms and lists.

This indicator provides the processing time for a completed transaction, including the total time and the time for each step. Select the icon to show and hide the response time details. Hover over the icon to see a tooltip with the
details. The following example shows the response time for retrieving a filtered list in a demo instance.  
Figure 1. Response time ![Response time (ms): 3326, network: 75, server: 1963, browser: 1288]()  
In this example, the transaction took the following amount of processing time:

* 3326 milliseconds total time
* 75 milliseconds moving data across the network
* 1963 milliseconds on the server  
  Note:  
  Server time is calculated using the following formula:  

      server time = (client response time - browser time - client network time)

* 1288 milliseconds in the browser, rendering the HTML and parsing and executing JavaScript
{#c_ResponseTimeOnForms__ul_lt3_l1b_fr}

A response time indicator doesn't appear for simple operations, such as paging or changing a list sort order. The response time indicator also doesn't appear for the first transaction in a session.

To view a detailed breakdown of the processing time on forms, select the response time indicator icon.  
Figure 2. Response time details

Administrators can disable the response time by setting the glide.ui.response_time property to false in the System Properties \[sys_properties\] table. In the navigation filter, enter
<kbd class="ph userinput">sys_properties.list</kbd> and search for glide.ui.response_time.

## Reviewing response times from system logs {#c_ResponseTimeOnForms__section_oxv_4tv_gfc}

You can use the system logs to review a list of response times for different transactions. To view the log, navigating to AllSystem Logs and select the relevant log type. When you review response times, look for the following issues.

1. A period where all transactions took an unusually long time. For example, transactions that normally took 1 second took 15 seconds between 11:00 AM and 11:20 AM. This issue can indicate that an unusual load, such as a large report, ran on that app server during that time.
2. A specific transaction which repeatedly took an unusually long time. For example, the list of closed incidents sorted by short description took 30 seconds each time it was displayed. This issue can indicate that a particular transaction put an unusual database load on the system, such as sorting 500,000 records on an unindexed field.
{#c_ResponseTimeOnForms__ol_aq3_dbb_fr}

If you notice issues with form response times, see [Improving response times on forms](https://servicenow-prod.fluidtopics.net/ZjIZpJU90oFWWnhJkENOnQ "Learn the techniques that can be used to improve form response times. If you notice latency or slow response times on forms, using these techniques can help improve performance.").

## Client transaction timings

The Client Transaction Timings plugin provides extra information about the time spent on both the client and server sides, by the browser and the network. This feature not only helps find long-running processes, but also
provides information about where in the process the performance issue is caused.

For more information, see [Client transaction timings](https://servicenow-prod.fluidtopics.net/eFWfa98kPozwpnQuADPe3g "The Client Transaction Timings plugin enhances the system logs by providing additional information about the durations of transactions taking place between the client and the server.").

*[\>]: and then