Page Comparison

...

Initial Checks

When SummitAI application performance issues are reported by the customer, the following activities need to be performed to check if it is a SummitAI Server/Application related issue or customer environment-related issue.

...

Access the Application directly from the SummitAI Application Server to check the performance of the Application. Access different pages, such as User Dashboard, New Incident, New SR, Incident details page, etc. These pages should in less than 5-6 seconds. Log a test Incident or update an Incident. These actions should complete within 6-7 seconds. If the Application is responding as per the expected response time, the SummitAI application is working fine. 

On Cloud

Access the Application using an office network or data card to check the Application performance. The on cloud customer instances should be accessible as per the above-mentioned response time. 

Checklist for Application Performance Issue

...

If any SQL management studio console is open and some transactions were executed but not committed will lock the tables and create performance issues. Please ensure all the MMC console is closed while testing the performance.

Some customers might complain about Application slowness at a specific time of the day or regular intervals. During the other times of the day, the Application performance might be normal. In such a scenario, validate the background jobs scheduled in the Application Server or Database Server (like denormalization, SLA calculation, Asset/AVM data posting, DB maintenance, Scheduled backups, VM backup, etc.). Identify the job, which is causing this issue and take appropriate fine-tuning action.

Some specific pages like Availability view and reports etc. could be slow due to different reasons like incorrect customer queries, incorrect version of SummitAI, too many records per views, no pagination set, no archival or records, etc. These cases need to be validated on a case-to-case basis.

Checklist for On-Premise Customers

1. Application, Proxy, DC, and Database server’s CPU and memory utilization: Check which component is occupying the resources.
2. Recycle the application pool if the utilization is still high, and then reset the IIS (Inform the users if other applications running on same IIS sever)
3. Check Network latency from the Application to the database and vice versa. Ping latency should not cross more than 5 milliseconds.
4. Check in the database if any continuous blockings are available by using the following queries:
   1. sp_who2 active
   2. select * from sysprocesses where blocked >0
5. Check the fragmentation level of all tables. If the fragmentation level is high check the maintenance job status.
6. Check if antivirus is blocking the Application, network traffic, or disk, etc.
7. Check for any long-running queries or jobs in the database.
8. Check if any patching is done on SummitAI servers.

Checklist for On Cloud Customers

1. What module(s) and pages are specifically reported as slow?
2. Check the internet speed
   1. Access the portal "http://speedtest.net".
   2. Change the Target Server by clicking Change Server.
   3. Based on the Azure Hosting, change this location.
   4. Click Go.
   5. Capture the Latency (ping), Download and upload.
   6. Page load time plugin on the chrome browser.
3. ​Traceroute to customer instance from Customer network.
   1. traceroute <customer instance URL without HTTP/https) or
   2. tracert <customer instance URL without HTTP/https)
4. Ping Report to any Public IPs, such as (ex: 8.8.8.8, 4.4.4.4) from the Customer System where the issue is reported.
   1. Azure latency report from the Customer System where the issue is reported (http://www.azurespeed.com/Azure/Latency​​).
5. Check for errors while accessing the SummitAI application.

...