This is a migrated thread and some comments may be shown as answers.

Stats & Determine Gateway, Where does it fit?

3 Answers 60 Views
Fiddler Classic
This is a migrated thread and some comments may be shown as answers.
Roger
Top achievements
Rank 1
Roger asked on 01 Apr 2015, 04:22 PM
Looking at the "Actual Performance" under the Statistics tab, I see (below).  Did it actually take a bit over a second to get past the autoproxy?  (Determine Gateway: 1076ms
).  If you look at ServerConnected: 11:31:55.814 then see FiddlerBeginRequest: 11:31:57.429 right after, this included the Determin Gateway time?  Overall Elapsed: 0:00:01.142 doesn't seem to add up.

ClientConnected: 11:31:55.322
ClientBeginRequest: 11:31:56.355
GotRequestHeaders: 11:31:56.355
ClientDoneRequest: 11:31:56.355
Determine Gateway: 1076ms
DNS Lookup: 0ms
TCP/IP Connect: 0ms
HTTPS Handshake: 0ms
ServerConnected: 11:31:55.814
FiddlerBeginRequest: 11:31:57.429
ServerGotRequest: 11:31:57.429
ServerBeginResponse: 11:31:57.494
GotResponseHeaders: 11:31:57.494
ServerDoneResponse: 11:31:57.497
ClientBeginResponse: 11:31:57.494
ClientDoneResponse: 11:31:57.497
Overall Elapsed: 0:00:01.142

3 Answers, 1 is accepted

Sort by
0
Eric Lawrence
Telerik team
answered on 01 Apr 2015, 06:38 PM
Hello, Roger--

The confusion here stems from the fact that this request was sent on a reused connection. The client finished sending the request to Fiddler at 11:31:56.355 and Fiddler finished returning the response at 11:31:57.497. Most of that time was the 1.076 seconds spent in figuring out what Server IP or Proxy IP to use; after that determination was made, a connection to reuse was pulled from the pool.

Spending over a second in Gateway determination is unusual and suggests something odd is going on in the client's non-Fiddler proxy configuration (e.g. a very slow PAC script).

Regards,
Eric Lawrence
Telerik
 

See What's Next in App Development. Register for TelerikNEXT.

 
0
Roger
Top achievements
Rank 1
answered on 01 Apr 2015, 06:46 PM
Thanks for the quick reply E Thanks for the quick reply Eirc.  "(e.g. a very slow PAC script)"...from your expereince, the PAC script may be too large?  What else would cause processing the PAC to be slow?

Roger

0
Eric Lawrence
Telerik team
answered on 01 Apr 2015, 09:49 PM
Hello, Roger--

A PAC Script would have to be HUGE to cause a problem. The typical reason that a PAC script runs slowly is when the script contains functions that perform DNS resolutions (e.g. dnsResolve or isInNet) https://www.websense.com/content/support/library/web/v76/pac_file_best_practices/PAC_best_pract.aspx

Regards,
Eric Lawrence
Telerik
 

See What's Next in App Development. Register for TelerikNEXT.

 
Tags
Fiddler Classic
Asked by
Roger
Top achievements
Rank 1
Answers by
Eric Lawrence
Telerik team
Roger
Top achievements
Rank 1
Share this question
or