Troubleshooting Slow Performance in portier Vision

1. System Resource Monitoring

Task Manager / Resource Monitor:

• Task Manager:Open Task Manager (Ctrl + Shift + Esc).Monitor CPU, memory, and disk usage during slow periods.Note any spikes or sustained high usage, particularly from the SQL Server process (sqlservr.exe) and the portier application.

  • Open Task Manager (Ctrl + Shift + Esc).

  • Monitor CPU, memory, and disk usage during slow periods.

  • Note any spikes or sustained high usage, particularly from the SQL Server process (sqlservr.exe) and the portier application.

• Resource Monitor:Open Resource Monitor from Task Manager (Performance tab -> Open Resource Monitor).Check detailed resource usage.

  • Open Resource Monitor from Task Manager (Performance tab -> Open Resource Monitor).

  • Check detailed resource usage.

Information to Provide:

• Screenshots or logs from Task Manager and Resource Monitor during slow periods.

• Details of any processes consuming excessive resources.

2. Network Performance

Ping Test:

• Open Command Prompt.

• Run continuous ping to the SQL Server to check for latency and packet loss. Command: ping -t [SQLServerIPAddress]

  • Command: ping -t [SQLServerIPAddress]

• Note any high latency or lost packets.

Traceroute:

• Open Command Prompt.

• Perform a traceroute to identify network hops and potential bottlenecks. Command: tracert [SQLServerIPAddress]

  • Command: tracert [SQLServerIPAddress]

Information to Provide:

• Results from the continuous ping test (latency, packet loss).

• Traceroute results highlighting any network delays.

3. SQL Server Performance

SQL Server Management Studio (SSMS):

• Activity Monitor:Open SSMS and connect to the SQL Server.Use the Activity Monitor to check for high CPU, memory usage, and I/O waits.Identify any blocking sessions or long-running queries.

  • Open SSMS and connect to the SQL Server.

  • Use the Activity Monitor to check for high CPU, memory usage, and I/O waits.

  • Identify any blocking sessions or long-running queries.

• Execution Plan:Capture the execution plan of slow-running queries.Instructions: In SSMS, right-click the query and select "Display Actual Execution Plan".

  • Capture the execution plan of slow-running queries.

  • Instructions: In SSMS, right-click the query and select "Display Actual Execution Plan".

Information to Provide:

• Screenshots or logs from Activity Monitor.

• Details of any blocking sessions or long-running queries.

• Execution plans for identified slow queries.

4. Event Logs

Event Viewer:

• Open Event Viewer (Windows Logs -> Application/System).

• Check for SQL Server-related errors or warnings.

Information to Provide:

• Relevant entries from Event Viewer, particularly errors and warnings related to SQL Server or network issues.

5. Performance Counters

Performance Monitor (PerfMon):

• Open Performance Monitor (type perfmon in Run dialog).

• Set up a data collector set to monitor key SQL Server performance counters: SQLServer:SQL StatisticsSQLServer:Buffer ManagerSQLServer:General Statistics

  • SQLServer:SQL Statistics

  • SQLServer:Buffer Manager

  • SQLServer:General Statistics

• Also monitor Network Interface and PhysicalDisk counters.

Information to Provide:

• Logs or screenshots of performance counter data.

• Any identified spikes or sustained high usage in key performance counters.

Summary

By following these steps and providing the requested information, your IT team can help identify potential causes of slow performance in the portier application. This collaborative approach ensures a quicker resolution and improves the overall experience.

For further assistance, please contact our support team with the collected data, and we will work with you to address any identified issues.