Udpcast February 2016

udpcast@udpcast.linux.lu

2 participants
4 discussions

Maximum async..
by Brent Kimberley 26 Feb '16

26 Feb '16

‎Hi Rich, Your implementation should be run well below "5GT/s".‎ * Look at the name plate of your back plane, storage‎, adapter, network adapter, logic, etc.‎.. * Check the data flow(s). * Determine Who is chewing up What - Where - Why - When - How - Rest ... * perhaps one or more of components are running in an energy efficient mode ;-) ‎ THIS MESSAGE IS FOR THE USE OF THE INTENDED RECIPIENT(S) ONLY AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, PROPRIETARY, CONFIDENTIAL, AND/OR EXEMPT FROM DISCLOSURE UNDER ANY RELEVANT PRIVACY LEGISLATION. No rights to any privilege have been waived. If you are not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying, conversion to hard copy, taking of action in reliance on or other use of this communication is strictly prohibited. If you are not the intended recipient and have received this message in error, please notify me by return e-mail and delete or destroy all copies of this message.

1 0

Re: [Udpcast] Udpcast Digest, Vol 123, Issue 1
by Brent Kimberley 25 Feb '16

25 Feb '16

>> We can't get the network transmission [to exceed] 2-3 % [of nameplate] What does iperf report? Have you tried a link local subnet? >> 1000Mbps Have you tried Send Unreliable Datagram(UD) with immediate (or multicast)? -----Original Message----- From: Brent Kimberley Sent: Wednesday, February 24, 2016 12:28 PM To: 'richard.k.evans(a)nasa.gov' Cc: udpcast(a)udpcast.linux.lu Subject: RE: Udpcast Digest, Vol 123, Issue 1 Hi Richard, Your performance on a general purpose machine should exceed the following. 384mbps @9000 395mbps @4096 352mbps @1456 312mbps @1024 193mbps @256 63mbps @64 Best Regards, Brent <snippet> @REM cd %TEMP% @REM fsutil file createnew test1.tx 2199023255552 @REM dir test1.tx @REM cd %TEMP% .\udp-sender.exe -b <blocksize> --autostart 5 --stat-period 2000 --max-bitrate 1000m --async --fec 8x8 --mcast-rdv-addr 127.0.0.1 --mcast-data-addr 127.0.0.1 --interface 127.0.0.1 --file test1.tx @REM cd %TEMP% .\udp-receiver.exe --file test.<blocksize>.rx --nosync --mcast-rdv-addr 127.0.0.1 --stat-period 2000 --interface 127.0.0.1 @REM del test*.* udp*.exe </snippet> < receiver observations> UDP receiver for test.64.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K ( 63.23 Mbps)) Transfer complete. UDP receiver for test.256.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (193.83 Mbps)) Transfer complete. UDP receiver for test.1024.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (312.40 Mbps) Transfer complete. UDP receiver for test.4096.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (395.57 Mbps)) Transfer complete. UDP receiver for test.9000.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (384.52 Mbps) Transfer complete. UDP receiver for test.1456.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (352.54 Mbps) Transfer complete. </receiver observations> Message: 1 Date: Thu, 18 Feb 2016 18:39:30 +0000 From: "Evans, Richard K. (GRC-H000)" <richard.k.evans(a)nasa.gov> To: "udpcast(a)udpcast.linux.lu" <udpcast(a)udpcast.linux.lu> Cc: "Evans, Richard K. \(GRC-H000\)" <richard.k.evans(a)nasa.gov> Subject: [Udpcast] maximum asynchronous speed and Jumbo Frames Message-ID: <DC3FB55EE7FEFD409A6FC1EA00D50D0B0F5C4510(a)NDJSMBX203.ndc.nasa.gov> Content-Type: text/plain; charset="iso-8859-1" Hello, I am using the UDPCast in asynchronous mode to transmit large data files through a Data Security Diode (mono-directional network). Here is the command we use to transmit: Udp-sender.exe --async --fec 8x8 --max-bitrate 1000m --mcast-rdv-addr 224.2.2.1 --mcast-data-addr 224.2.2.2 --interface <ipTx> --file myfile.dat The Receive command I use is: udp-receiver.exe --nosync --mcast-rdv-addr 224.2.2.1 --interface <ipRx> --f myfile.dat Overall, this works well but we have noticed that we can't get the network transmission speed up above 2-3 % (22Mbps) of the Gigabit Ethernet adapter's full capability (1000Mbps). We also know that we are not processor limited, nor are we disk speed limited or anything else we can think of. I know that the asynchronous mode application is for satellite transmissions that are understandably slower than what a file transfer purely over Gibabit Ethernet can do, so I am writing here to ask if any one has any thoughts or insights about what might be the core issue that keeps the process running so slow. Fwiw, the Data Security Diode is a Canary GT-10SD, but for tuning UDPCast, we bypass the diode with a direct cable connection between Tx and Rx machines. So the performance of the system I am describing is without the diode in place. Thanks in advance, folks. -Rich - Richard Evans, NASA GRC - Plum Brook Station ? http://www.linkedin.com/in/rkevans ???216.973.4398 ------------------------------ _______________________________________________ Udpcast mailing list Udpcast(a)udpcast.linux.lu https://www.udpcast.linux.lu/mailman/listinfo/udpcast End of Udpcast Digest, Vol 123, Issue 1 *************************************** THIS MESSAGE IS FOR THE USE OF THE INTENDED RECIPIENT(S) ONLY AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, PROPRIETARY, CONFIDENTIAL, AND/OR EXEMPT FROM DISCLOSURE UNDER ANY RELEVANT PRIVACY LEGISLATION. No rights to any privilege have been waived. If you are not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying, conversion to hard copy, taking of action in reliance on or other use of this communication is strictly prohibited. If you are not the intended recipient and have received this message in error, please notify me by return e-mail and delete or destroy all copies of this message.

2 1

Re: [Udpcast] Udpcast Digest, Vol 123, Issue 1
by Brent Kimberley 24 Feb '16

24 Feb '16

Hi Richard, Your performance on a general purpose machine should exceed the following. 384mbps @9000 395mbps @4096 352mbps @1456 312mbps @1024 193mbps @256 63mbps @64 Best Regards, Brent <snippet> @REM cd %TEMP% @REM fsutil file createnew test1.tx 2199023255552 @REM dir test1.tx @REM cd %TEMP% .\udp-sender.exe -b <blocksize> --autostart 5 --stat-period 2000 --max-bitrate 1000m --async --fec 8x8 --mcast-rdv-addr 127.0.0.1 --mcast-data-addr 127.0.0.1 --interface 127.0.0.1 --file test1.tx @REM cd %TEMP% .\udp-receiver.exe --file test.<blocksize>.rx --nosync --mcast-rdv-addr 127.0.0.1 --stat-period 2000 --interface 127.0.0.1 @REM del test*.* udp*.exe </snippet> < receiver observations> UDP receiver for test.64.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K ( 63.23 Mbps)) Transfer complete. UDP receiver for test.256.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (193.83 Mbps)) Transfer complete. UDP receiver for test.1024.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (312.40 Mbps) Transfer complete. UDP receiver for test.4096.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (395.57 Mbps)) Transfer complete. UDP receiver for test.9000.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (384.52 Mbps) Transfer complete. UDP receiver for test.1456.rx at 127.0.0.1 on Software Loopback Interface 1 Connected as #0 to 127.0.0.1 bytes= 2 097 152K (352.54 Mbps) Transfer complete. </receiver observations> Message: 1 Date: Thu, 18 Feb 2016 18:39:30 +0000 From: "Evans, Richard K. (GRC-H000)" <richard.k.evans(a)nasa.gov> To: "udpcast(a)udpcast.linux.lu" <udpcast(a)udpcast.linux.lu> Cc: "Evans, Richard K. \(GRC-H000\)" <richard.k.evans(a)nasa.gov> Subject: [Udpcast] maximum asynchronous speed and Jumbo Frames Message-ID: <DC3FB55EE7FEFD409A6FC1EA00D50D0B0F5C4510(a)NDJSMBX203.ndc.nasa.gov> Content-Type: text/plain; charset="iso-8859-1" Hello, I am using the UDPCast in asynchronous mode to transmit large data files through a Data Security Diode (mono-directional network). Here is the command we use to transmit: Udp-sender.exe --async --fec 8x8 --max-bitrate 1000m --mcast-rdv-addr 224.2.2.1 --mcast-data-addr 224.2.2.2 --interface <ipTx> --file myfile.dat The Receive command I use is: udp-receiver.exe --nosync --mcast-rdv-addr 224.2.2.1 --interface <ipRx> --f myfile.dat Overall, this works well but we have noticed that we can't get the network transmission speed up above 2-3 % (22Mbps) of the Gigabit Ethernet adapter's full capability (1000Mbps). We also know that we are not processor limited, nor are we disk speed limited or anything else we can think of. I know that the asynchronous mode application is for satellite transmissions that are understandably slower than what a file transfer purely over Gibabit Ethernet can do, so I am writing here to ask if any one has any thoughts or insights about what might be the core issue that keeps the process running so slow. Fwiw, the Data Security Diode is a Canary GT-10SD, but for tuning UDPCast, we bypass the diode with a direct cable connection between Tx and Rx machines. So the performance of the system I am describing is without the diode in place. Thanks in advance, folks. -Rich - Richard Evans, NASA GRC - Plum Brook Station ? http://www.linkedin.com/in/rkevans ???216.973.4398 ------------------------------ _______________________________________________ Udpcast mailing list Udpcast(a)udpcast.linux.lu https://www.udpcast.linux.lu/mailman/listinfo/udpcast End of Udpcast Digest, Vol 123, Issue 1 *************************************** THIS MESSAGE IS FOR THE USE OF THE INTENDED RECIPIENT(S) ONLY AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, PROPRIETARY, CONFIDENTIAL, AND/OR EXEMPT FROM DISCLOSURE UNDER ANY RELEVANT PRIVACY LEGISLATION. No rights to any privilege have been waived. If you are not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying, conversion to hard copy, taking of action in reliance on or other use of this communication is strictly prohibited. If you are not the intended recipient and have received this message in error, please notify me by return e-mail and delete or destroy all copies of this message.

1 0

maximum asynchronous speed and Jumbo Frames
by Evans, Richard K. (GRC-H000) 18 Feb '16

18 Feb '16

Hello, I am using the UDPCast in asynchronous mode to transmit large data files through a Data Security Diode (mono-directional network). Here is the command we use to transmit: Udp-sender.exe --async --fec 8x8 --max-bitrate 1000m --mcast-rdv-addr 224.2.2.1 --mcast-data-addr 224.2.2.2 --interface <ipTx> --file myfile.dat The Receive command I use is: udp-receiver.exe --nosync --mcast-rdv-addr 224.2.2.1 --interface <ipRx> --f myfile.dat Overall, this works well but we have noticed that we can't get the network transmission speed up above 2-3 % (22Mbps) of the Gigabit Ethernet adapter's full capability (1000Mbps). We also know that we are not processor limited, nor are we disk speed limited or anything else we can think of. I know that the asynchronous mode application is for satellite transmissions that are understandably slower than what a file transfer purely over Gibabit Ethernet can do, so I am writing here to ask if any one has any thoughts or insights about what might be the core issue that keeps the process running so slow. Fwiw, the Data Security Diode is a Canary GT-10SD, but for tuning UDPCast, we bypass the diode with a direct cable connection between Tx and Rx machines. So the performance of the system I am describing is without the diode in place. Thanks in advance, folks. -Rich - Richard Evans, NASA GRC - Plum Brook Station http://www.linkedin.com/in/rkevans ©216.973.4398

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Udpcast February 2016