Reviewing response time on forms
Summarize
Summary of Reviewing response time on forms
ServiceNow provides a response time indicator on many forms and lists to help you monitor the processing time of completed transactions. This indicator shows the total transaction time and a detailed breakdown of each step involved, including network transfer, server processing, and browser rendering. This tool enables administrators to identify and troubleshoot performance issues effectively.
Show less
Key Features
- Response Time Indicator: A clock icon appears at the end of forms and lists. Clicking it toggles detailed response time information, and hovering over it reveals a tooltip with summary details.
- Detailed Breakdown: Displays total processing time, network time, server time (calculated by subtracting browser and network times from client response time), and browser time spent rendering and executing JavaScript.
- Limitations: The indicator does not appear for simple operations like paging or sorting lists and is not shown for the first transaction in a session.
- Configurable: Administrators can disable the response time indicator by setting the
glide.ui.responsetimeproperty to false in the System Properties [sysproperties] table. - System Logs for Response Times: Response times for various transactions can be reviewed in system logs under All > System Logs. This helps identify periods of unusually long transaction times or specific transactions that consistently perform poorly.
- Client Transaction Timings Plugin: Provides advanced insights into timing on client and server sides, including browser and network delays, helping pinpoint the exact cause of performance issues.
Practical Use for ServiceNow Customers
By utilizing the response time indicator and reviewing system logs, ServiceNow administrators can quickly detect and analyze performance bottlenecks on forms and lists. This helps improve user experience by addressing slow transactions caused by network issues, server load, or inefficient queries. The Client Transaction Timings plugin further enhances troubleshooting by detailing where delays occur in the transaction process.
To manage or disable these indicators, administrators can adjust system properties, providing flexibility based on organizational needs. For persistent performance problems, the response time data offers a starting point to optimize form responsiveness and system efficiency.
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.
- 3326 milliseconds total time
- 75 milliseconds moving data across the network
- 1963 milliseconds on the serverNote: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
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.
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 sys_properties.list and search for glide.ui.response_time.
Reviewing response times from system logs
- 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.
- 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.
If you notice issues with form response times, see Improving response times on forms.
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.