IIS Connection Time
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 28.000000000000004%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Андрей Петров
1
Reputation point
Hi Everyone,
Can someone help me to troubleshoot IIS connection time problems.
Right now we have 4 servers with IIS and balance traffic for them using NGinx+
So when connection comes IIS writes into the log data for the POST requests with 200 as a resukt and the duration of this request.
However some connections take more than regular time approximatelly x10 - x100
For example normal time is 30ms and some strange cases happen with time 1300ms for example.
For them we switched on additional logging using this article:
https://learn.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/using-failed-request-tracing-rules-to-troubleshoot-application-request-routing-arr
And got very detailed reports.
However all the steps inside have 0ms duration and this is out of sense :-) Looks like we did something wrong?
Also we think that some new connections may trigger new sessions and in that case new database connectivity that may take time. How to manage this delays? Is there any chance to configure some connection pooling to establish some set of them in the beginning and make keepalive connectivity to them?
Thank you.
Windows development | Internet Information Services
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 24%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff2022-12-23T02:32:03.433+00:00 However all the steps inside have 0ms duration and this is out of sense :-) Looks like we did something wrong?
First make sure the request you want to see is captured by the failed request trace, second, make sure the xml log file you open corresponds to your current website.
-
Андрей Петров 1 Reputation point
2022-12-26T11:58:52.83+00:00 For sure we checked that particular request and thats why we ask here how to properly configure such tool and see what takes so mych time and this pareticular server where the trace was created.
-
Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff
2022-12-27T09:38:01.75+00:00 How are you using failed request tracking? Unless the current request is not captured, the time of the request will be included in the trace of the failed request.
You can try open a case via: https://support.microsoft.com, one of our engineers will help find the root cause.
-
Андрей Петров 1 Reputation point
2022-12-27T10:31:01.437+00:00 So we have enabled failed request tracking on particular site, conditions are path - *, all associated providers, all status codes, time taken - 00:00:01 (supposed to track all request processing longer than 1 second).
And request get recorded, request summary shows 1328 msec, but when we go to request details, Complete Request Trace shows 0 msec, please refer to screenshots attached.
-
Sam Wu-MSFT 7,566 Reputation points Microsoft External Staff
2022-12-29T09:57:59.747+00:00 I think your request might be hang in iis, you can try the following command to see if you can get some useful information.
%windir%system32inetsrvappcmd list requests /elapsed:30000
Sign in to comment
Sign in to answer