Am I reaching a limit?
-
:mad: :mad: I am using TCP/IP socket, one application is running on Windows 2000, the other is on VxWorks(a real-time OS). What I am doing is: the Win app will send the VxWorks a request, say REQ_1, VxWorks received REQ_1, send back an acknoledge RESPONSE_1, Win app received RESPONSE_1, will send several KB data to VxWorks. so the data flow is:
Win App VxWorks
REQ_1 ------------> (wait for reqeust)
(wait for response) <------------ RESPONSE_1
data -------------> (wait for data)I found out that the first round of handshaking is very fast, it takes almost no time to finish everything (0.000000 according the my TRACE statement). But the second will take 0.08 or 0.09 or 0.10 seconds, and the following one would take 0.2 seconds. So there will be a limit 5 times of handshaking in a seconds. The bottleneck is for the Win App to receive the RESPONSE_1. I tested it on a 10M LAN as well as on a 100M LAN, and get the same result. X| Am I reaching any limit of software handshaking of TCP/IP socket? What did I do wrong? :((
-
:mad: :mad: I am using TCP/IP socket, one application is running on Windows 2000, the other is on VxWorks(a real-time OS). What I am doing is: the Win app will send the VxWorks a request, say REQ_1, VxWorks received REQ_1, send back an acknoledge RESPONSE_1, Win app received RESPONSE_1, will send several KB data to VxWorks. so the data flow is:
Win App VxWorks
REQ_1 ------------> (wait for reqeust)
(wait for response) <------------ RESPONSE_1
data -------------> (wait for data)I found out that the first round of handshaking is very fast, it takes almost no time to finish everything (0.000000 according the my TRACE statement). But the second will take 0.08 or 0.09 or 0.10 seconds, and the following one would take 0.2 seconds. So there will be a limit 5 times of handshaking in a seconds. The bottleneck is for the Win App to receive the RESPONSE_1. I tested it on a 10M LAN as well as on a 100M LAN, and get the same result. X| Am I reaching any limit of software handshaking of TCP/IP socket? What did I do wrong? :((
-
Are you using TCP_NODELAY (turns off the Nagle algorithm) in the socket options? In Windows this defaults to 0.2 second delay for a send - I am not sure about VxWorks.
-
Are you using TCP_NODELAY (turns off the Nagle algorithm) in the socket options? In Windows this defaults to 0.2 second delay for a send - I am not sure about VxWorks.
Damn it, I thought it was the Nagle algorithm getting in the way, but I wasn't sure at all so I didn't say anything... :mad: :laugh: Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?
-
Damn it, I thought it was the Nagle algorithm getting in the way, but I wasn't sure at all so I didn't say anything... :mad: :laugh: Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?