Socket Ping vs Connect Performance
-
Hi All, We have quite about 30 clients connecting to about 200 servers on our WAN. Currently we are experiencing extremely slow connection establishment times, in the order of 15-20 seconds. However, a ping from a client to the same server responds in 1-2 seconds. The client and server applications are based on WSASocket. I have traced the client and server side applications to death and it seams that the delay is in the receiving of the FD_ACCEPT event. Once the event has been received and the connections established, all seems fine, but it takes an unusually long time for the event to be received (through WSAEnumNetworkEvents). Are there any reasons for the connection establishment to take SOOOO long, while a ping goes through quite quickly ? Thanks OD
-
Hi All, We have quite about 30 clients connecting to about 200 servers on our WAN. Currently we are experiencing extremely slow connection establishment times, in the order of 15-20 seconds. However, a ping from a client to the same server responds in 1-2 seconds. The client and server applications are based on WSASocket. I have traced the client and server side applications to death and it seams that the delay is in the receiving of the FD_ACCEPT event. Once the event has been received and the connections established, all seems fine, but it takes an unusually long time for the event to be received (through WSAEnumNetworkEvents). Are there any reasons for the connection establishment to take SOOOO long, while a ping goes through quite quickly ? Thanks OD
Sounds strange, maybe your routers do some traffic shaping or you hit a bottleneck in your network infrastructure. I would try to send more dummy data with the connection handshake (to see if that has a negative or positive impact), plus try another listening port number. /M
My Webchat in Europe :java: