Performance debugging from version 9306 onwards
On Performance/Crash Issues, we have one URL to generate all debug details, this is applicable from 9306 onwards.
Need to execute the URL in the browser, which has already login session into the application
http(s)://<hostname>:<port>/servlet/PerformanceDebug
Works even Server is not responding*
Takes thread dump, running queries, locked queries ( pgsql and mssql only ), connection dump
Once files generated, will get message
New to ADSelfService Plus?
Related Articles
Performance Debug
For Performance/slowness issues instead of taking Threaddump manually or instead of invoking PerformanceTool make use of the below URL when the issue occurs, http://servername:portnumber/servlet/PerformanceDebug The above URL works even when the ...
SQL Server High CPU - To collect queries consuming CPU resources
1. To get an idea of how much CPU the queries are currently using, out of overall CPU capacity, run the following statement: DECLARE @init_sum_cpu_time int, @utilizedCpuCount int --get CPU count used by SQL Server SELECT @utilizedCpuCount = COUNT( * ...
Basic Performance Issues RCA On Postgres DB Cx
Whenever cx faces slowness in PG SQL Setup, below are the first step of actions to check and proceed based on our previous performance tickets. 1. Antivirus are main cause of slowness, high CPU, and memory consumption of PGSQL in many cx tickets. ...
Inputs required for analyzing Performance Issues
We need a couple of details to analyze Performance issue. So, please send the below details : Below mentioned details should be gathered before restarting the application. 1. Let us know whether you are taking Scheduled full backup or backup without ...
High CPU Utilization during Backup
Cause: From 14740, below listed parameters will no longer be included in the command. As a result, when performing backups, 7-Zip utilizes a high number of CPU threads, leading to increased CPU usage. mmt - Sets number of CPU threads mmemuse - Sets a ...