The System Diagnostics application is one of the places to look for root causes of performance issues. The Diagnostics page is used to generate an overview of useful diagnostic information about a running instance and cluster nodes. To see how much memory each node is using, you can use the stats page for each node in System Diagnostics, which lists the available and in-use memory. Bear in mind that memory use will fluctuate, and it's not uncommon for it to reach beyond 95% usage before memory garbage collection reduces it back to normal levels.

Since Fall 2010 Stable 1, the performance of individual threads is now tracked by the instance, and can be viewed by administrators. Thread performance can be monitored in two places: 

• the Performance Graph Set
• the transaction log

Running stats.do and threads.do is very useful when trying to identify and isolate the cause of a performance issue, specifically when your instance is presenting a low available central processing unit (CPU) percentage or a high number of transactions waiting to be processed. The information in the stats.do page matches up with the information in the threads.do page.

To gather stats and threads:

1. On your browser, navigate to http://<InstanceName>.service-now.com/stats.do. The <InstanceName> should be populated to reflect the instance that is presenting slow response times. 

   Alternately, log in to your instance and navigate to System Diagnostics > Stats.

1. Open a new tab or window in your browser and navigate to http://<InstanceName>.service-now.com/threads.do.

   Alternately, log in to your instance and in the Type filter text field, enter threads.do and press Enter.

1. Press Command + s on your Mac or ctrl + s on your Windows PC to save the stats.do and threads.do pages to your desktop.

1. On the incident form, click the Attachments  icon to add the files to the incident record.

For more information, see the following product documentation pages:

• System Diagnostics
• Monitoring Performance on Threads
• Performance Metrics

For more topic related issues, see Troubleshooting slow performance.