>> Another big potential source of latency on startup is the DNS lookup. A
>> few bad DNS servers in the lookup path, or a misconfigured name service
>> switch config could potentially add up to 40 seconds of delay.
>> Subsequent connects wouldn't see that delay because the results would be
>> cached for a while.
> According to the logs, client resolves the ip and connects to 443 port w/o delay. it is the start of ssl handshake failing to kick of for a long time.
>
>

The DNS delay could be on the server side - is the server maybe doing
some reverse lookups or similar? Do you have access to the server logs
and/or configuration?

What happens if you repeat the test immediately - i.e. start the test
process where the first connection has the delay and let that move onto
the next connections which work ok, stop the process and then start it
again right away. Does the first connection still have the delay?

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-11-27