Stats & Determine Gateway, Where does it fit?

4 posts, 0 answers
  1. Roger
    Roger avatar
    2 posts
    Member since:
    Apr 2015

    Posted 01 Apr 2015 Link to this post

    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
  2. Eric Lawrence
    Admin
    Eric Lawrence avatar
    833 posts

    Posted 01 Apr 2015 Link to this post

    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.

     
  3. Roger
    Roger avatar
    2 posts
    Member since:
    Apr 2015

    Posted 01 Apr 2015 in reply to Eric Lawrence Link to this post

    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

  4. Eric Lawrence
    Admin
    Eric Lawrence avatar
    833 posts

    Posted 01 Apr 2015 Link to this post

    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.

     
Back to Top