Hi All,
Which performance counters gets affected due to high spikes in Pingdom response time and New Relic Request Queuing?
We have found below counters which goes high when high Request Queuing is observed.
1) .NET CLR LocksAndThreads(w3wp)\Contention Rate / sec
2) ASP.NET Apps v2.0.50727(_LM_W3SVC_2_ROOT)\Requests Executing
3) ASP.NET v2.0.50727\Requests Current
4) ASP.NET v2.0.50727\Requests Queued
5) .NET CLR Memory(w3wp)\Finalization Survivors
Below counters surely goes very high when very high Request Queuing is observed.
6) Processor(_Total)\% Processor Time
7) Process(w3wp)\% Processor Time
8) .NET CLR LocksAndThreads(w3wp)\Current Queue Length
9) ASP.NET Apps v2.0.50727(_LM_W3SVC_2_ROOT)\Pipeline Instance Count
Please feel free to rectify us if above findings are incorrect.
And please do suggest other performance counters for spikes in Pingdom response time as well as high spikes in request queuing in New Relic ?
We need appropriate performance counters to take dump with help of DebugDiag ?
Any help is appreciated.
Awaiting your reply.
Thanks,
Sandeepkumar Gupta