ServerConnected is later than ServerBeginResponse!!!

[Mohammadvali]

I did a load test performance for an application, and sends many requests to the server through different concurrent users. Some requests failed and returned 504. However, I'm wondering about the time factors, and don't understand the followings:

A) There is an elapsed time about 1 minute between ClientDoneRequest and ServerConnected. I try to understand why I experience this 1 minute gap, what indicates, and how to interpret it/

1) ClientDoneRequest:13:06:11.336

2) ServerConnected:13:07:11.241

 

B) The other question is that the serverConnected is later than ServerBeginResponse! How is it possible?

1) ServerConnected:13:07:11.241

2) ServerBeginResponse:13:07:11.134

I copied the entire timing below:

 

NOTE: This request was retried after a Receive operation failed.

ClientConnected:13:04:28.914
ClientBeginRequest:13:06:10.972
GotRequestHeaders:13:06:10.972
ClientDoneRequest:13:06:11.336
Determine Gateway:0ms
DNS Lookup: 0ms
TCP/IP Connect:0ms
HTTPS Handshake:52ms
ServerConnected:13:07:11.241
FiddlerBeginRequest:13:07:11.294
ServerGotRequest:13:07:11.294
ServerBeginResponse:13:07:11.134
GotResponseHeaders:00:00:00.000
ServerDoneResponse:13:08:19.817
ClientBeginResponse:13:08:19.819
ClientDoneResponse:13:08:19.819

Overall Elapsed:0:02:08.846

[Alexander]

Hi,

Please, excuse us for the delay in our answer.

A) ClientDoneRequest is the timestamp at which Fiddler completed reading the request from the client. ServerConnected is the timestamp at which connection to the server was established. Knowing those lead us to the conclusion that Fiddler needed a whole minute to connect to the server (maybe due to the many requests coming at it at the same time) after receiving the request from the client.

B) It seems that this is bug in Fiddler. An item on our backlog will be added for this one. Thank you for reporting it.

Regards,
Alexander
Progress Telerik