1Gbit UDP
-
Hi all ! I'm trying to send and receive data between 2 computers (Windows 2003 Server OS) using UDP packets through 1Gbit cable. I tried using several UDP packet sizes and compare the data received to the data sent - however it always fails (the comparison) after some time (from few mili's to few minutes). The broadband reaches about 80% - which means it is about 800Mgbit per second data rate. Why it fails ? Is it something to do with UDP ? Maybe the network device driver cannot handle this rate ? How can I know where is the problem ? Thanks in advanced, :confused: amit
-
Hi all ! I'm trying to send and receive data between 2 computers (Windows 2003 Server OS) using UDP packets through 1Gbit cable. I tried using several UDP packet sizes and compare the data received to the data sent - however it always fails (the comparison) after some time (from few mili's to few minutes). The broadband reaches about 80% - which means it is about 800Mgbit per second data rate. Why it fails ? Is it something to do with UDP ? Maybe the network device driver cannot handle this rate ? How can I know where is the problem ? Thanks in advanced, :confused: amit
The UDP packet sizes may be too large. General,ethernet device's MTU is 1500 Bytes,so UDP data sizes must be <=1472 Bytes(IP header+UDP header=28Bytes). If one UDP packet sizes more than etherner MTU, IP must be fragmentation. In general,UDP packet sizes less than 512 Bytes is limited. But like NFS,can be more than 8192 Bytes in LAN. Just you said that the broadband reaches about 80%,which means etherner device rate is 1000Mb. So network device driver can handle this rate. Have an effect on ethernet device driver handle: IP fragmentation,CRC check, memoey buffer,CPU rate,packet gap,time delay,and so on.
-
Hi all ! I'm trying to send and receive data between 2 computers (Windows 2003 Server OS) using UDP packets through 1Gbit cable. I tried using several UDP packet sizes and compare the data received to the data sent - however it always fails (the comparison) after some time (from few mili's to few minutes). The broadband reaches about 80% - which means it is about 800Mgbit per second data rate. Why it fails ? Is it something to do with UDP ? Maybe the network device driver cannot handle this rate ? How can I know where is the problem ? Thanks in advanced, :confused: amit
Are you aware that UDP packets aren't guaranteed to be delivered? You should consider changing to TCP/IP.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
The UDP packet sizes may be too large. General,ethernet device's MTU is 1500 Bytes,so UDP data sizes must be <=1472 Bytes(IP header+UDP header=28Bytes). If one UDP packet sizes more than etherner MTU, IP must be fragmentation. In general,UDP packet sizes less than 512 Bytes is limited. But like NFS,can be more than 8192 Bytes in LAN. Just you said that the broadband reaches about 80%,which means etherner device rate is 1000Mb. So network device driver can handle this rate. Have an effect on ethernet device driver handle: IP fragmentation,CRC check, memoey buffer,CPU rate,packet gap,time delay,and so on.
Hi Obafemi Martins ! first of all thanks for your answer - it helped me. When sending I now use an exact MTU packet size (of 9k in my network - I use jumbo size frames) and it works great (no fragmentation is needed) without losses even in high bandwidth. But... The sender MUST send messages of 64K size (Hardware Limits) - so I will not be able to avoid ip fragmentation. How to overcome this issue ? Is it possible to be working when ip fregmatation occurs without any losses ? what can be done ? Thanks in advanced, Amit C.
