One of the top findings in the Response Time Hotspots is the IIS Modules and specifically the ManagedPipelineHandler
On investigating some of the slow purepaths, I could find in the code "Aggregated IIS Events - ManagedPipelineHandler" with very high Self-Time sometimes up to 7 - 12 seconds which is almost 90% of the response time of the purepath.
I tried researching about the ManagePipelineHandler but could not reach a conclusion of whether this is something to do with the IIS configuration or if this is something in the code that makes this IIS module consume a lot of time or is there something hanging?
Any pointers to what the problem might be?
Hello, ManagedPipelineHandler is IIS module which routes transaction to proper part of IIS. If this module is not able to do it, transaction stuck on MPH. This is result of issue, not root cause. Look for transactions on IIS which stuck and keep threads busy. For example where do you have problems with communication to external services, MQ, DB etc.