You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(83) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(29) |
Feb
(43) |
Mar
(9) |
Apr
(9) |
May
(21) |
Jun
(43) |
Jul
(32) |
Aug
(12) |
Sep
(17) |
Oct
(29) |
Nov
(9) |
Dec
(15) |
2004 |
Jan
(8) |
Feb
(48) |
Mar
(50) |
Apr
(37) |
May
(12) |
Jun
(14) |
Jul
(33) |
Aug
(26) |
Sep
(16) |
Oct
(38) |
Nov
(39) |
Dec
(12) |
2005 |
Jan
(5) |
Feb
(22) |
Mar
(19) |
Apr
(24) |
May
(34) |
Jun
(21) |
Jul
(38) |
Aug
(14) |
Sep
(39) |
Oct
(25) |
Nov
(28) |
Dec
(18) |
2006 |
Jan
(19) |
Feb
(17) |
Mar
(47) |
Apr
(14) |
May
(27) |
Jun
(33) |
Jul
(3) |
Aug
(29) |
Sep
(12) |
Oct
(6) |
Nov
(8) |
Dec
(7) |
2007 |
Jan
(6) |
Feb
(11) |
Mar
(8) |
Apr
(7) |
May
(17) |
Jun
(24) |
Jul
(20) |
Aug
(25) |
Sep
(6) |
Oct
(7) |
Nov
(8) |
Dec
(5) |
2008 |
Jan
(7) |
Feb
(9) |
Mar
(22) |
Apr
(22) |
May
(33) |
Jun
(10) |
Jul
(15) |
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(8) |
Dec
(5) |
2009 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(5) |
May
(4) |
Jun
(5) |
Jul
(5) |
Aug
(6) |
Sep
(2) |
Oct
(7) |
Nov
(11) |
Dec
(12) |
2010 |
Jan
|
Feb
(16) |
Mar
(27) |
Apr
(40) |
May
(13) |
Jun
(11) |
Jul
(10) |
Aug
(8) |
Sep
(9) |
Oct
(2) |
Nov
(5) |
Dec
(6) |
2011 |
Jan
(9) |
Feb
|
Mar
(17) |
Apr
(15) |
May
(4) |
Jun
(10) |
Jul
(9) |
Aug
(4) |
Sep
(4) |
Oct
(11) |
Nov
(12) |
Dec
(4) |
2012 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
(9) |
May
(6) |
Jun
|
Jul
(6) |
Aug
(6) |
Sep
(3) |
Oct
(1) |
Nov
(3) |
Dec
(8) |
2013 |
Jan
(2) |
Feb
(4) |
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(6) |
Aug
(2) |
Sep
(2) |
Oct
(10) |
Nov
(4) |
Dec
(3) |
2014 |
Jan
(3) |
Feb
(17) |
Mar
(5) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(5) |
Aug
(36) |
Sep
(51) |
Oct
(2) |
Nov
(8) |
Dec
(6) |
2015 |
Jan
(26) |
Feb
(3) |
Mar
(9) |
Apr
(2) |
May
|
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
(3) |
2016 |
Jan
|
Feb
(9) |
Mar
|
Apr
|
May
|
Jun
(13) |
Jul
(16) |
Aug
(8) |
Sep
(2) |
Oct
(11) |
Nov
(7) |
Dec
|
2017 |
Jan
(25) |
Feb
(8) |
Mar
(8) |
Apr
(3) |
May
(12) |
Jun
(18) |
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
(1) |
Dec
(1) |
2018 |
Jan
(2) |
Feb
(8) |
Mar
(2) |
Apr
(28) |
May
(32) |
Jun
(7) |
Jul
(11) |
Aug
(11) |
Sep
(18) |
Oct
(4) |
Nov
(9) |
Dec
(4) |
2019 |
Jan
(6) |
Feb
|
Mar
|
Apr
(1) |
May
(13) |
Jun
(13) |
Jul
(1) |
Aug
(6) |
Sep
(9) |
Oct
(9) |
Nov
(1) |
Dec
(5) |
2020 |
Jan
(2) |
Feb
(7) |
Mar
(2) |
Apr
(8) |
May
(3) |
Jun
(6) |
Jul
(11) |
Aug
(10) |
Sep
(3) |
Oct
(3) |
Nov
(6) |
Dec
(23) |
2021 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
(13) |
Jul
(2) |
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
|
2022 |
Jan
(3) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
(4) |
Aug
(4) |
Sep
(2) |
Oct
(1) |
Nov
(1) |
Dec
|
2023 |
Jan
(2) |
Feb
(8) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
(16) |
Oct
|
Nov
(1) |
Dec
(2) |
2024 |
Jan
|
Feb
|
Mar
(2) |
Apr
(3) |
May
(5) |
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Jason M. <sab...@gm...> - 2022-09-22 21:39:25
|
I'm having some trouble interpreting the UDP test results and was wondering if someone could correct/guide me? I am using all the defaults and connecting from the client to the server using UDP. I am confused because it looks like the client is sending 16 datagrams per second for 10 seconds, a total of 160 datagrams. However, the server and client indicate that only 159 were sent/received, and 0 were lost. Client results: [ ID] Interval Transfer Bandwidth Total Datagrams [ 4] 0.00-1.01 sec 128 KBytes 1.04 Mbits/sec 16 [ 4] 1.01-2.01 sec 128 KBytes 1.06 Mbits/sec 16 [ 4] 2.01-3.01 sec 128 KBytes 1.04 Mbits/sec 16 [ 4] 3.01-4.01 sec 128 KBytes 1.05 Mbits/sec 16 [ 4] 4.01-5.01 sec 128 KBytes 1.04 Mbits/sec 16 [ 4] 5.01-6.01 sec 128 KBytes 1.06 Mbits/sec 16 [ 4] 6.01-7.01 sec 128 KBytes 1.04 Mbits/sec 16 [ 4] 7.01-8.01 sec 128 KBytes 1.06 Mbits/sec 16 [ 4] 8.01-9.01 sec 128 KBytes 1.04 Mbits/sec 16 [ 4] 9.01-10.01 sec 128 KBytes 1.05 Mbits/sec 16 - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 4] 0.00-10.01 sec 1.25 MBytes 1.05 Mbits/sec 9.575 ms 0/159 (0%) Server results: [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 5] 0.00-1.01 sec 104 KBytes 846 Kbits/sec 12.745 ms 0/13 (0%) [ 5] 1.01-2.00 sec 144 KBytes 1.18 Mbits/sec 19.201 ms 0/18 (0%) [ 5] 2.00-3.00 sec 112 KBytes 921 Kbits/sec 17.153 ms 0/14 (0%) [ 5] 3.00-4.00 sec 136 KBytes 1.11 Mbits/sec 16.183 ms 0/17 (0%) [ 5] 4.00-5.00 sec 128 KBytes 1.05 Mbits/sec 19.292 ms 0/16 (0%) [ 5] 5.00-6.00 sec 136 KBytes 1.11 Mbits/sec 17.524 ms 0/17 (0%) [ 5] 6.00-7.00 sec 128 KBytes 1.05 Mbits/sec 15.414 ms 0/16 (0%) [ 5] 7.00-8.00 sec 128 KBytes 1.05 Mbits/sec 12.795 ms 0/16 (0%) [ 5] 8.00-9.01 sec 128 KBytes 1.04 Mbits/sec 12.340 ms 0/16 (0%) [ 5] 9.01-10.00 sec 128 KBytes 1.06 Mbits/sec 9.575 ms 0/16 (0%) [ 5] 10.00-10.08 sec 0.00 Bytes 0.00 bits/sec 9.575 ms 0/0 (0%) - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams [ 5] 0.00-10.08 sec 0.00 Bytes 0.00 bits/sec 9.575 ms 0/159 (0%) |
From: SHARRAH, L. E <ls...@at...> - 2022-08-17 02:36:32
|
Can anyone tell me if iperf3 is designed to be used with cellular technology and if so what command should I be running. I’ve been running these two commands for ethernet and getting great results. iperf3 -c xxx.xxx.xxx.xxx -i 2 -t 20 -w 230K -P 3 iperf3 -c xxx.xxx.xxx.xxx -i 2 -t 20 -w 230K -P 3 -R LOWELL E. SHARRAH Professional-Network Support Service Experience & Operations 221 N Washington Sq. Lansing, MI 48933 O: (517) 281-1443 ls...@at...<mailto:ls...@at...> [cid:image001.jpg@01D8B189.3B95AB50] Confidential This e-mail and any files transmitted with it are the property of AT&T and/or its affiliates, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient (s) or otherwise have reason to believe that you have received this message in error, please notify the sender at 517-281-1443 and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. From: Bob McMahon via Iperf-users <ipe...@li...> Sent: Sunday, August 07, 2022 12:31 AM To: iPerf User Group <ipe...@li...> Cc: Rpm <rp...@li...> Subject: [Iperf-users] iperf 2 responsiveness test in 2.1.8-rc, --bounceback option Hi All, I've added a low impact, low duty cycle responsiveness test to iperf 2. Man page is here.<https://iperf2.sourceforge.io/iperf-manpage.html> [rjmcmahon@bobcat iperf2-code]$ iperf -v iperf version 2.1.8-rc (6 August 2022) pthreads [rjmcmahon@bobcat iperf2-code]$ iperf -s --permit-key=mytest -P 1 --hide-ips ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) Permit key is 'mytest' (timeout in 20.0 seconds) ------------------------------------------------------------ [rjmcmahon@ryzen3950 iperf2-code]$ iperf -c hostname -i 1 --bounceback --permit-key=mytest --hide-ips ------------------------------------------------------------ Client connecting to (**hidden**), TCP port 5001 Bursting: 100 Byte writes 10 times every 1.00 second(s) Bounce-back test (size= 100 Byte) (server hold req=0 usecs) TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [mytest(1)] local *.*.*.96 port 38048 connected with *.*.*.123 port 5001 (bb len/hold=100/0) (icwnd/mss/irtt=14/1448/15038) [ ID] Interval Transfer Bandwidth BB cnt=avg/min/max/stdev Rtry Cwnd/RTT RPS [mytest(1)] 0.00-1.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.333/9.247/15.596/2.493 ms 0 14K/11667 us 88 rps [mytest(1)] 1.00-2.00 sec 1.95 KBytes 16.0 Kbits/sec 10=10.164/9.340/13.791/1.417 ms 0 14K/10374 us 98 rps [mytest(1)] 2.00-3.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.301/9.321/14.310/2.010 ms 0 14K/10796 us 88 rps [mytest(1)] 3.00-4.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.242/9.432/14.401/2.128 ms 0 14K/10720 us 88 rps [mytest(1)] 4.00-5.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.576/9.558/14.442/2.196 ms 0 14K/10821 us 86 rps [mytest(1)] 5.00-6.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.310/9.514/14.615/2.151 ms 0 14K/10806 us 88 rps [mytest(1)] 6.00-7.00 sec 1.95 KBytes 16.0 Kbits/sec 10=10.944/9.310/14.490/2.233 ms 0 14K/10548 us 91 rps [mytest(1)] 7.00-8.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.584/9.468/19.286/3.254 ms 0 14K/10794 us 86 rps [mytest(1)] 8.00-9.00 sec 1.95 KBytes 16.0 Kbits/sec 10=10.987/9.378/14.322/2.139 ms 0 14K/10533 us 90 rps [mytest(1)] 9.00-10.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.449/9.930/14.722/2.151 ms 0 14K/10832 us 87 rps [mytest(1)] 0.00-10.03 sec 19.5 KBytes 15.9 Kbits/sec 100=11.189/9.247/19.286/2.190 ms 0 14K/11083 us 89 rps [ 1] 0.00-10.03 sec BB8(f)-PDF: bin(w=100us):cnt(100)=93:1,94:9,95:5,96:11,97:9,98:2,99:5,100:6,101:9,102:3,103:3,104:1,105:1,106:2,107:1,115:1,129:1,130:1,132:1,137:1,138:2,139:3,141:4,142:2,143:4,144:3,145:4,147:2,148:1,156:1,193:1 (5.00/95.00/99.7%=94/147/193,Outliers=0,obl/obu=0/0) Bob This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: Bob M. <bob...@br...> - 2022-08-16 20:30:35
|
How about something like 'Iperf Next Evolution 2022 (iperf2) <https://sourceforge.net/projects/iperf2/>' I'm very open to better suggestions. Thanks, Bob On Tue, Aug 16, 2022 at 1:04 PM Sebastian Moeller <moe...@gm...> wrote: > Ho Bob, > > +1 for renaming; the iperf2 iperf3 things is really confusing for mere end > users. > > However "next generation/NG" is a relative moniker, in a few years NG is > going to be the new normal and hence the name misleading again. > > While somewhat lame, maybe "iperformance" might be better in side stepping > the-bigger-is-better issue when including numbers in the name, or obviously > the correct answer go directly to iperf42 ;) > > Regards > Sebastian > > > > On Aug 16, 2022, at 20:54, Bob McMahon via Make-wifi-fast < > mak...@li...> wrote: > > > > Hi All, > > > > It's unfortunate that numbers have been used in iperf naming. Many think > iperf3 is the next version of iperf (or iperf2.) The number in the name > isn't a version number as iperf 2 and iperf 3 are different code bases, > different developers, have different goals, and don't interoperate. > > > > I'm thinking it's a good time to break this number as part of the name > and only use -v for version numbers. In that context, I'm thinking about > renaming iperf 2 to iperf next generation. The "next generation" implies > that are lots of new features around responsiveness and latency. > > > > This proposed name will be used in web sites, etc. The "iperf2" binary > will still just be iperf. I'm also hoping to get an IANA service as 'iperf' > that way any device that supports the iperf 2.1.8 can also advertise > responsiveness support. > > > > Here is an example and proposed updates to sourceforge. My hope is that > this will help clear up the confusion between the two different tools. > > > > Comments? > > Bob > > > > This electronic communication and the information and any files > transmitted with it, or attached to it, are confidential and are intended > solely for the use of the individual or entity to whom it is addressed and > may contain information that is confidential, legally privileged, protected > by privacy laws, or otherwise restricted from disclosure to anyone else. If > you are not the intended recipient or the person responsible for delivering > the e-mail to the intended recipient, you are hereby notified that any use, > copying, distributing, dissemination, forwarding, printing, or copying of > this e-mail is strictly prohibited. If you received this e-mail in error, > please return the e-mail to the sender, delete it from your computer, and > destroy any printed copy of > it._______________________________________________ > > Make-wifi-fast mailing list > > Mak...@li... > > https://lists.bufferbloat.net/listinfo/make-wifi-fast > > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: Bob M. <bob...@br...> - 2022-08-16 18:55:01
|
Hi All, It's unfortunate that numbers have been used in iperf naming. Many think iperf3 is the next version of iperf (or iperf2.) The number in the name isn't a version number as iperf 2 and iperf 3 are different code bases, different developers, have different goals, and don't interoperate. I'm thinking it's a good time to break this number as part of the name and only use -v for version numbers. In that context, I'm thinking about renaming iperf 2 to iperf next generation. The "next generation" implies that are lots of new features around responsiveness and latency. This proposed name will be used in web sites, etc. The "iperf2" binary will still just be iperf. I'm also hoping to get an IANA service as 'iperf' that way any device that supports the iperf 2.1.8 can also advertise responsiveness support. Here is an example and proposed updates to sourceforge. <https://sourceforge.net/projects/iperf2/> My hope is that this will help clear up the confusion between the two different tools. Comments? Bob -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: Bob M. <bob...@br...> - 2022-08-07 04:31:21
|
Hi All, I've added a low impact, low duty cycle responsiveness test to iperf 2. Man page is here. <https://iperf2.sourceforge.io/iperf-manpage.html> [rjmcmahon@bobcat iperf2-code]$ iperf -v iperf version 2.1.8-rc (6 August 2022) pthreads [rjmcmahon@bobcat iperf2-code]$ iperf -s --permit-key=mytest -P 1 --hide-ips ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) Permit key is 'mytest' (timeout in 20.0 seconds) ------------------------------------------------------------ [rjmcmahon@ryzen3950 iperf2-code]$ iperf -c hostname -i 1 --bounceback --permit-key=mytest --hide-ips ------------------------------------------------------------ Client connecting to (**hidden**), TCP port 5001 Bursting: 100 Byte writes 10 times every 1.00 second(s) Bounce-back test (size= 100 Byte) (server hold req=0 usecs) TCP window size: 16.0 KByte (default) ------------------------------------------------------------ [mytest(1)] local *.*.*.96 port 38048 connected with *.*.*.123 port 5001 (bb len/hold=100/0) (icwnd/mss/irtt=14/1448/15038) [ ID] Interval Transfer Bandwidth BB cnt=avg/min/max/stdev Rtry Cwnd/RTT RPS [mytest(1)] 0.00-1.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.333/9.247/15.596/2.493 ms 0 14K/11667 us 88 rps [mytest(1)] 1.00-2.00 sec 1.95 KBytes 16.0 Kbits/sec 10=10.164/9.340/13.791/1.417 ms 0 14K/10374 us 98 rps [mytest(1)] 2.00-3.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.301/9.321/14.310/2.010 ms 0 14K/10796 us 88 rps [mytest(1)] 3.00-4.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.242/9.432/14.401/2.128 ms 0 14K/10720 us 88 rps [mytest(1)] 4.00-5.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.576/9.558/14.442/2.196 ms 0 14K/10821 us 86 rps [mytest(1)] 5.00-6.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.310/9.514/14.615/2.151 ms 0 14K/10806 us 88 rps [mytest(1)] 6.00-7.00 sec 1.95 KBytes 16.0 Kbits/sec 10=10.944/9.310/14.490/2.233 ms 0 14K/10548 us 91 rps [mytest(1)] 7.00-8.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.584/9.468/19.286/3.254 ms 0 14K/10794 us 86 rps [mytest(1)] 8.00-9.00 sec 1.95 KBytes 16.0 Kbits/sec 10=10.987/9.378/14.322/2.139 ms 0 14K/10533 us 90 rps [mytest(1)] 9.00-10.00 sec 1.95 KBytes 16.0 Kbits/sec 10=11.449/9.930/14.722/2.151 ms 0 14K/10832 us 87 rps [mytest(1)] 0.00-10.03 sec 19.5 KBytes 15.9 Kbits/sec 100=11.189/9.247/19.286/2.190 ms 0 14K/11083 us 89 rps [ 1] 0.00-10.03 sec BB8(f)-PDF: bin(w=100us):cnt(100)=93:1,94:9,95:5,96:11,97:9,98:2,99:5,100:6,101:9,102:3,103:3,104:1,105:1,106:2,107:1,115:1,129:1,130:1,132:1,137:1,138:2,139:3,141:4,142:2,143:4,144:3,145:4,147:2,148:1,156:1,193:1 (5.00/95.00/99.7%=94/147/193,Outliers=0,obl/obu=0/0) Bob -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: Bob M. <bob...@br...> - 2022-07-16 19:56:15
|
Iperf 2 site has a man page. Make install will install the man page per the latest version. You'll want to compile from source for bounceback. Branch of master or 2-1-8-rc has that code. It will be generally released with 2.1.8 when that's complete and fully tested. https://iperf2.sourceforge.io/iperf-manpage.html https://sourceforge.net/p/iperf2/code/ci/master/tree/doc/CLOCKSYNC_NOTES Bob On Sat, Jul 16, 2022, 1:07 AM Ohad Vano <oha...@gm...> wrote: > I am interested in measuring network latency over TCP connection. > Where can I find documentation for these flags? (such as the --boundback > or --trip-times) > Can't find these on the iperf website documentation. > > Ohad > > > On Sat, Jul 16, 2022 at 12:40 AM Bob McMahon <bob...@br...> > wrote: > >> "IPerf 2 <https://sourceforge.net/projects/iperf2/> is different from >> the iperf3 <https://github.com/esnet/iperf>. Each can be used to measure >> network performance, however, they DO NOT interoperate. They are completely >> independent implementations with different strengths, different options, >> and different capabilities. Both are under active development" >> >> iperf 2 latency & one way delay (OWD) results are reliable assuming one >> has synchronized the clocks to a common reference. Tests such as >> --bounceback don't require clock sync as it uses a TCP round trip >> measurement, i.e. write() to read() and back. >> >> Bob >> >> On Fri, Jul 15, 2022 at 1:16 PM Ohad Vano <oha...@gm...> wrote: >> >>> Hi, >>> >>> I can't find a way to measure latency over TCP using iperf3. I think >>> that this feature is supported in iperf2. Why isn't this supported in >>> iperf3? Are the iperf2 results reliable? >>> >>> Thanks, >>> Ohad >>> _______________________________________________ >>> Iperf-users mailing list >>> Ipe...@li... >>> https://lists.sourceforge.net/lists/listinfo/iperf-users >>> >> >> This electronic communication and the information and any files >> transmitted with it, or attached to it, are confidential and are intended >> solely for the use of the individual or entity to whom it is addressed and >> may contain information that is confidential, legally privileged, protected >> by privacy laws, or otherwise restricted from disclosure to anyone else. If >> you are not the intended recipient or the person responsible for delivering >> the e-mail to the intended recipient, you are hereby notified that any use, >> copying, distributing, dissemination, forwarding, printing, or copying of >> this e-mail is strictly prohibited. If you received this e-mail in error, >> please return the e-mail to the sender, delete it from your computer, and >> destroy any printed copy of it. > > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: Ohad V. <oha...@gm...> - 2022-07-16 08:08:04
|
I am interested in measuring network latency over TCP connection. Where can I find documentation for these flags? (such as the --boundback or --trip-times) Can't find these on the iperf website documentation. Ohad On Sat, Jul 16, 2022 at 12:40 AM Bob McMahon <bob...@br...> wrote: > "IPerf 2 <https://sourceforge.net/projects/iperf2/> is different from the > iperf3 <https://github.com/esnet/iperf>. Each can be used to measure > network performance, however, they DO NOT interoperate. They are completely > independent implementations with different strengths, different options, > and different capabilities. Both are under active development" > > iperf 2 latency & one way delay (OWD) results are reliable assuming one > has synchronized the clocks to a common reference. Tests such as > --bounceback don't require clock sync as it uses a TCP round trip > measurement, i.e. write() to read() and back. > > Bob > > On Fri, Jul 15, 2022 at 1:16 PM Ohad Vano <oha...@gm...> wrote: > >> Hi, >> >> I can't find a way to measure latency over TCP using iperf3. I think that >> this feature is supported in iperf2. Why isn't this supported in iperf3? >> Are the iperf2 results reliable? >> >> Thanks, >> Ohad >> _______________________________________________ >> Iperf-users mailing list >> Ipe...@li... >> https://lists.sourceforge.net/lists/listinfo/iperf-users >> > > This electronic communication and the information and any files > transmitted with it, or attached to it, are confidential and are intended > solely for the use of the individual or entity to whom it is addressed and > may contain information that is confidential, legally privileged, protected > by privacy laws, or otherwise restricted from disclosure to anyone else. If > you are not the intended recipient or the person responsible for delivering > the e-mail to the intended recipient, you are hereby notified that any use, > copying, distributing, dissemination, forwarding, printing, or copying of > this e-mail is strictly prohibited. If you received this e-mail in error, > please return the e-mail to the sender, delete it from your computer, and > destroy any printed copy of it. |
From: Bob M. <bob...@br...> - 2022-07-15 22:08:27
|
"IPerf 2 <https://sourceforge.net/projects/iperf2/> is different from the iperf3 <https://github.com/esnet/iperf>. Each can be used to measure network performance, however, they DO NOT interoperate. They are completely independent implementations with different strengths, different options, and different capabilities. Both are under active development" iperf 2 latency & one way delay (OWD) results are reliable assuming one has synchronized the clocks to a common reference. Tests such as --bounceback don't require clock sync as it uses a TCP round trip measurement, i.e. write() to read() and back. Bob On Fri, Jul 15, 2022 at 1:16 PM Ohad Vano <oha...@gm...> wrote: > Hi, > > I can't find a way to measure latency over TCP using iperf3. I think that > this feature is supported in iperf2. Why isn't this supported in iperf3? > Are the iperf2 results reliable? > > Thanks, > Ohad > _______________________________________________ > Iperf-users mailing list > Ipe...@li... > https://lists.sourceforge.net/lists/listinfo/iperf-users > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: Ohad V. <oha...@gm...> - 2022-07-15 20:13:51
|
Hi, I can't find a way to measure latency over TCP using iperf3. I think that this feature is supported in iperf2. Why isn't this supported in iperf3? Are the iperf2 results reliable? Thanks, Ohad |
From: Bob M. <bob...@br...> - 2022-06-29 19:10:11
|
I can speak to iperf 2 but not iperf 3. It depends on the goals. If the goal is to test throughput only, then the hardware requirements are driven by the ability to saturate the link under test. If the links are 10G or above, and speaking for iperf 2, the -P option will use multiple traffic threads so more cores will help. If the goals include measuring one way delay (OWD) then the hardware needs a way to synchronize the system clocks to a common reference. We use the GPS atomic clock since it's somewhat available over the globe. In general, iperf users (and blog authors) are behind. We find that latency really needs attention from the industry at large. Seems like too few understand this aspect of network performance (and user experience) and seem to be stuck on throughput-only measurements. Bob On Wed, Jun 29, 2022 at 11:37 AM ChenWei Hung <Che...@mi...> wrote: > Hello, > > We are trying to set up our own Iperf server for speed testing. What are > the hardware requirements for Iperf server? > > > > Thank you, > > > > Chen-Wei > > *ChenWei Hung * > Intern - Network Technician > > Office: > Che...@mi... > > *Midco.com* > > _______________________________________________ > Iperf-users mailing list > Ipe...@li... > https://lists.sourceforge.net/lists/listinfo/iperf-users > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: ChenWei H. <Che...@mi...> - 2022-06-29 18:34:31
|
Hello, We are trying to set up our own Iperf server for speed testing. What are the hardware requirements for Iperf server? Thank you, Chen-Wei [http://images.midcocomm.com/ES_MidcoLogo.png] ChenWei Hung Intern - Network Technician Office: Che...@mi... Midco.com |
From: Bob M. <bob...@br...> - 2022-06-17 22:21:59
|
I've added a few more options to the iperf 2 bounceback test around responsiveness & working load. CLIENT SPECIFIC OPTIONS --bounceback run a tcp bounceback test (set size with -l or --len, defaults to 100 bytes) --bounceback-congest[=up|down|bidir][,n] request a concurrent working load or TCP stream(s), defaults to full duplex (or bidir) unless the up or down option is provided. The number of TCP streams defaults to 1 and can be changed via the n value, e.g. --bounceback-congest=down,4 will use four TCP streams from server to the client as the working load. The IP ToS will be BE (0x0) for working load traffic. Also, thanks to Dave Taht and some WMM QoS guys, I've added symbolic names to the --tos and --tos-override support. IP tos: Specifies the type-of-service or DSCP class for connections. Accepted values are af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cs0, cs1, cs2, cs3, cs4, cs5, cs6, cs7, ef, le, nqb, nqb2, ac_be, ac_bk, ac_vi, ac_vo, lowdelay, throughput, reliability, a numeric value, or none to use the operating system default. The ac_xx values are the four access categories defined in WMM for Wi-Fi, and they are aliases for DSCP values that will be mapped to the corresponding ACs under the assumption that the de‐ vice uses the DSCP-to-UP mapping table specified in IETF RFC 8325. Thanks, Bob -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: Ankita A. K. <Ank...@ex...> - 2022-03-30 05:33:51
|
Hi, I executed iperf3 on RPI4(aarch64) and FU540 (RISCV64). I see huge difference in results of both. RPI4= 84.8 GBytes FU540=5.47Gbytes. I want to know why there is degradation on Fu540. So what are the ways to find it out? Thanks |
From: Sarah L. <swl...@es...> - 2022-02-08 01:44:37
|
ESnet (Energy Sciences Network) is proud to announce the availability of iperf 3.11. This release is primarily a bugfix release. A few new features added, most notably discussions on GitHub are now supported. More information can be found in the iperf-3.11 release notes, which are contained in the RELNOTES.md file in the distribution. iperf 3.11 should be fully backward-compatible with prior iperf3 releases, that is, iperf 3.11 clients and servers should interoperate correctly with all 3.x clients and servers. iperf3 is a tool for measuring the maximum TCP, UDP, and SCTP throughput along a path, allowing for the tuning of various parameters and reporting measurements such as throughput, jitter, and datagram packet loss. It is fully supported on Linux, FreeBSD, and macOS. It may run on other platforms as well, although it has not received the same attention and testing. Note that iperf3 is not compatible with, and will not interoperate with, version 2 or earlier of iperf, although the two versions can co-exist on the same hosts and networks. The source code for iperf 3.11 is available at: https://downloads.es.net/pub/iperf/iperf-3.11.tar.gz SHA256 hash: de8cb409fad61a0574f4cb07eb19ce1159707403ac2dc01b5d175e91240b7e5f iperf3 is freely-redistributable under a 3-clause BSD license. More information can be found in the LICENSE file inside the source distribution. Additional documentation for iperf3 can be found at: https://software.es.net/iperf More information about iperf3 (including the issue tracker, source code repository access, and mailing list) can be found on the iperf3 page on GitHub at: https://github.com/esnet/iperf User questions can go to the iperf users list (which is more-or-less shared between iperf2 and iperf3): ipe...@li... Mailing list information and archives can be found at: https://lists.sourceforge.net/lists/listinfo/iperf-users The mailing list for iperf3 development is: ipe...@go... To see the list archives or join the mailing list, visit: http://groups.google.com/group/iperf-dev |
From: Sarah L. <swl...@es...> - 2022-02-02 20:44:58
|
ESnet (Energy Sciences Network) is proud to announce the availability of iperf 3.11. This release is primarily a bugfix release. A few new features added, most notably discussions on GitHub are now supported. More information can be found in the iperf-3.11 release notes, which are contained in the RELNOTES.md file in the distribution. iperf 3.11 should be fully backward-compatible with prior iperf3 releases, that is, iperf 3.11 clients and servers should interoperate correctly with all 3.x clients and servers. iperf3 is a tool for measuring the maximum TCP, UDP, and SCTP throughput along a path, allowing for the tuning of various parameters and reporting measurements such as throughput, jitter, and datagram packet loss. It is fully supported on Linux, FreeBSD, and macOS. It may run on other platforms as well, although it has not received the same attention and testing. Note that iperf3 is not compatible with, and will not interoperate with, version 2 or earlier of iperf, although the two versions can co-exist on the same hosts and networks. The source code for iperf 3.11 is available at: https://downloads.es.net/pub/iperf/iperf-3.11.tar.gz SHA256 hash: de8cb409fad61a0574f4cb07eb19ce1159707403ac2dc01b5d175e91240b7e5f iperf3 is freely-redistributable under a 3-clause BSD license. More information can be found in the LICENSE file inside the source distribution. Additional documentation for iperf3 can be found at: https://software.es.net/iperf More information about iperf3 (including the issue tracker, source code repository access, and mailing list) can be found on the iperf3 page on GitHub at: https://github.com/esnet/iperf User questions can go to the iperf users list (which is more-or-less shared between iperf2 and iperf3): ipe...@li... Mailing list information and archives can be found at: https://lists.sourceforge.net/lists/listinfo/iperf-users The mailing list for iperf3 development is: ipe...@go... To see the list archives or join the mailing list, visit: http://groups.google.com/group/iperf-dev |
From: Zvi V. <ver...@gm...> - 2022-01-11 04:10:03
|
Hi Bob, Thank you very much ! Best regards, Zvika On Mon, Jan 10, 2022 at 5:27 PM Bob McMahon <bob...@br...> wrote: > You may want to use iperf3 for this. Iperf2 is quite complex and the only > authoritative information comes from the source code itself. A brief & > incomplete design doc is here. > > https://sourceforge.net/p/iperf2/code/ci/master/tree/doc/DESIGN_NOTES > > Bob > > On Mon, Jan 10, 2022, 4:31 AM Zvi Vered <ver...@gm...> wrote: > >> Hello, >> >> I have to write a TCP server application that should respond to iperf in >> client mode running under windows. >> >> The server side runs with lwip under TI's TIVA. >> >> Can you please provide the ICD that I should handle in the server side ? >> >> Thank you, >> Zvika >> _______________________________________________ >> Iperf-users mailing list >> Ipe...@li... >> https://lists.sourceforge.net/lists/listinfo/iperf-users >> > > This electronic communication and the information and any files > transmitted with it, or attached to it, are confidential and are intended > solely for the use of the individual or entity to whom it is addressed and > may contain information that is confidential, legally privileged, protected > by privacy laws, or otherwise restricted from disclosure to anyone else. If > you are not the intended recipient or the person responsible for delivering > the e-mail to the intended recipient, you are hereby notified that any use, > copying, distributing, dissemination, forwarding, printing, or copying of > this e-mail is strictly prohibited. If you received this e-mail in error, > please return the e-mail to the sender, delete it from your computer, and > destroy any printed copy of it. |
From: Bob M. <bob...@br...> - 2022-01-10 15:52:48
|
You may want to use iperf3 for this. Iperf2 is quite complex and the only authoritative information comes from the source code itself. A brief & incomplete design doc is here. https://sourceforge.net/p/iperf2/code/ci/master/tree/doc/DESIGN_NOTES Bob On Mon, Jan 10, 2022, 4:31 AM Zvi Vered <ver...@gm...> wrote: > Hello, > > I have to write a TCP server application that should respond to iperf in > client mode running under windows. > > The server side runs with lwip under TI's TIVA. > > Can you please provide the ICD that I should handle in the server side ? > > Thank you, > Zvika > _______________________________________________ > Iperf-users mailing list > Ipe...@li... > https://lists.sourceforge.net/lists/listinfo/iperf-users > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: Zvi V. <ver...@gm...> - 2022-01-10 09:28:22
|
Hello, I have to write a TCP server application that should respond to iperf in client mode running under windows. The server side runs with lwip under TI's TIVA. Can you please provide the ICD that I should handle in the server side ? Thank you, Zvika |
From: Bob M. <bob...@br...> - 2021-10-25 17:12:39
|
There are some slides on the sourceforge site https://sourceforge.net/projects/iperf2/files/Iperf%202.0.13%20Enhancements.pdf/download https://sourceforge.net/projects/iperf2/files/Iperf%202.0.14%20New%20Features.pdf/download Bob On Mon, Oct 25, 2021 at 3:00 AM karima smida <kar...@gm...> wrote: > Hi all, > Please, can you provide a tutorial on how to use iperf to measure > throughput of video streaming and web browsing applications. > Thank you in advance. > > -- > Karima SMIDA > PhD Student > Mediatron > *SupCom* > _______________________________________________ > Iperf-users mailing list > Ipe...@li... > https://lists.sourceforge.net/lists/listinfo/iperf-users > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: karima s. <kar...@gm...> - 2021-10-25 09:57:39
|
Hi all, Please, can you provide a tutorial on how to use iperf to measure throughput of video streaming and web browsing applications. Thank you in advance. -- Karima SMIDA PhD Student Mediatron *SupCom* |
From: Cise M. <ci...@si...> - 2021-10-19 06:42:28
|
Dear all, please find below the final call for contributions for MHV'22 (deadline extended to Friday). The venue is most appropriate for multimedia topics that can benefit from an industry-academia collaboration, and measurements + insights from the networking community would be of great interest. If you have any questions, please do not hesitate to contact the TPC co-chair Christian Timmerer (chr...@aa...). Best, Cise * *ACM Mile High Video (MHV) 2022* *March 1-3, 2022, Denver, CO* *Web site*: https://mile-high.video/call.php *Abstract submission deadline: Oct. 22, 2021* *Prospective speakers are invited to submit an abstract (i.e., approx. 400 words or up to one page using the ACM template) that will be peer-reviewed by the ACM MHV technical program committee (TPC) for relevance, timeliness and technical correctness.* After running as an independent event for several years, starting with 2022, Mile High Video (MHV) will be organized by the ACM Special Interest Group on Multimedia (SIGMM) to grow further. ACM MHV’22 will establish a unique forum for participants from both industry and academia to present, share and discuss innovations from content production to consumption. ACM MHV’22 welcomes contributions from industry to share real-world problems and solutions as well as novel approaches and results from basic research typically conducted within an academic environment. ACM MHV’22 will provide a unique opportunity to view the interplay of the industry and academia in the area of video technologies. *ACM MHV contributions are solicited in, but not limited to the following areas:* • Content production, encoding and packaging • Encoding for broadcast, mobile and OTT, and using AI/ML in encoding • New and developing audio and video codecs • HDR, accessibility • Quality assessment models and tools, and user experience studies • Workflows • Virtualized headends, cloud-based workflows for production and distribution • Redundancy and resilience in content origination • Ingest protocols • Ad insertion • Content delivery and security • Developments in transport protocols and new delivery paradigms • Protection for OTT distribution and tools against piracy • Analytics • Streaming technologies • Adaptive streaming and transcoding • Low latency • Player, playback and UX developments • Content discovery, promotion and recommendation systems • Protocol and Web API improvements and innovations for streaming video • Industry trends • Advances in interactive and immersive (xR) video • Video coding for machines • Cloud gaming and gaming streaming • Provenance, content authentication and deepfakes • Standards and interoperability • New and developing standards in the media and delivery space • Interoperability guidelines *Prospective speakers are invited to submit an abstract (i.e., approx. 400 words or up to one page using the ACM template) that will be peer-reviewed by the ACM MHV technical program committee (TPC) for relevance, timeliness and technical correctness.* The authors of the accepted abstracts will be invited to optionally submit a full-length paper (up to six pages + references) for possible inclusion into the conference proceedings. These papers must be original work (i.e., not published previously in a journal or conference) and will also be peer-reviewed by the ACM MHV TPC. Accepted abstracts and full-length papers will be presented at the ACM MHV conference and will be published in the conference proceedings in the ACM Digital Library. All prospective ACM authors are subject to all ACM Publications Policies, including ACM's new Publications Policy on Research Involving Human Participants and Subjects. *How to Submit an Abstract* Prospective authors are invited to submit an abstract here: https://mhv22.hotcrp.com/ *Important Dates*• *Abstract submission deadline: Oct. 22, 2021* • Notification of abstract acceptance: Nov. 15, 2021 • (Optional) Full-length paper submission deadline: Nov. 30, 2021 • Notification of full-length paper acceptance: Dec. 31, 2021 • Camera-ready submission (abstracts/full-length papers) deadline: Jan. 31, 2022 *ACM MHV’22 Program Chairs*• Christian Timmerer (AAU; christian.timmerer AT aau.at) • Dan Grois (Comcast; dgrois AT acm.org) *ACM MHV'22 Program Committee Members* • Florence Agboma (Sky, UK) • Saba Ahsan (Nokia, Finland) • Ali C. Begen (Ozyegin University, Turkey) • Imed Bouazizi (Qualcomm, USA) • Alan Bovik (University of Texas at Austin, USA) • Pablo Cesar (CWI, The Netherlands) • Pankaj Chaudhari (Hulu, USA) • Luca De Cicco (Politecnico di Bari, Italy) • Jan De Cock (Synamedia, Belgium) • Thomas Edwards (Amazon Web Services, USA) • Christian Feldmann (Bitmovin, Germany) • Simone Ferlin-Reiter (Ericsson, Sweden) • Carsten Griwodz (University of Oslo, Norway) • Sally Hattori (Disney, USA) • Carys Hughes (Sky, UK) • Mourad Kioumgi (Sky, Germany) • Will Law (Akamai, USA) • Zhu Li (University of Missouri, Kansas City, USA) • Zhi Li (Netflix, USA) • John Luther (JW Player, USA) • Maria Martini (Kingston University, UK) • Rufael Mekuria (Unified Streaming, The Netherlands) • Marta Mrak (BBC, UK) • Matteo Naccari (Audinate, UK) • Mark Nakano (WarnerMedia, USA) • Sejin Oh (Dolby, USA) • Mickael Raulet (ATEME, France) • Christian Rothenberg (University of Campinas , Brazil) • Lucile Sassatelli (Universite Cote d'Azur, France) • Tamar Shoham (Beamr, Israel) • Gwendal Simon (Synamedia, France) • Lea Skorin-Kapov (University of Zagreb, Croatia) • Michael Stattmann (castLabs, Germany) • Nicolas Weil (Amazon Web Services, USA) • Roger Zimmermann (NUS, Singapore) *ACM MHV Steering Committee Members* • Balu Adsumilli (YouTube, USA) • Ali C. Begen (Ozyegin University, Turkey), Co-chair • Alex Giladi (Comcast, USA), Co-chair • Sally Hattori (Walt Disney Studios, USA) • Jean-Baptiste Kempf (VideoLAN, France) • Thomas Kernen (NVIDIA, Switzerland) • Scott Labrozzi (Disney Streaming Services, USA) • Maria Martini (Kingston University, UK) • Hatice Memiguven (beIN Media, Turkey) • Ben Mesander (Wowza Media Systems, USA) • Mark Nakano (WarnerMedia, USA) • Madeleine Noland (ATSC, USA) • Yuriy Reznik (Brightcove, USA) • Tamar Shoham (Beamr, Israel) -- Cise Midoglu Simula Research Laboratory https://www.simula.no |
From: Bob M. <bob...@br...> - 2021-10-04 18:53:37
|
Testing QUIC is of interest to iperf 2 community. It would be good to gauge interests as well as understand any other options to test QUIC. I would like to verify that iperf is the best tool for this. Comments around that would be helpful. Bob On Mon, Oct 4, 2021 at 9:54 AM HARISH KUMAR Ivaturi < har...@gm...> wrote: > Hi > > Based on this iperf draft document which has been released recently on how > to calculate throughput of QUIC (in a pure networking side) Framework for > QUIC Throughput Testing (ietf.org) > <https://www.ietf.org/id/draft-corre-quic-throughput-testing-00.html#name-measuring-quic-throughput> > > I believe there is a possible way to introduce quic flag and run it for > bidirectional traffic for server and client in order to get more throughput > value. > > Can Iperf developers make this open source and release a solution on this? > > Thanks > > BR > Harish Kumar > _______________________________________________ > Iperf-users mailing list > Ipe...@li... > https://lists.sourceforge.net/lists/listinfo/iperf-users > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |
From: HARISH K. I. <har...@gm...> - 2021-10-04 17:17:38
|
Hi Bob Thanks a lot for your reply. You all can do this. BR Harish Kumar On Mon, 4 Oct, 2021, 7:09 pm Bob McMahon, <bob...@br...> wrote: > Testing QUIC is of interest to iperf 2 community. It would be good to > gauge interests as well as understand any other options to test QUIC. I > would like to verify that iperf is the best tool for this. Comments > around that would be helpful. > > Bob > > On Mon, Oct 4, 2021 at 9:54 AM HARISH KUMAR Ivaturi < > har...@gm...> wrote: > >> Hi >> >> Based on this iperf draft document which has been released recently on >> how to calculate throughput of QUIC (in a pure networking side) Framework >> for QUIC Throughput Testing (ietf.org) >> <https://www.ietf.org/id/draft-corre-quic-throughput-testing-00.html#name-measuring-quic-throughput> >> >> I believe there is a possible way to introduce quic flag and run it for >> bidirectional traffic for server and client in order to get more throughput >> value. >> >> Can Iperf developers make this open source and release a solution on this? >> >> Thanks >> >> BR >> Harish Kumar >> _______________________________________________ >> Iperf-users mailing list >> Ipe...@li... >> https://lists.sourceforge.net/lists/listinfo/iperf-users >> > > This electronic communication and the information and any files > transmitted with it, or attached to it, are confidential and are intended > solely for the use of the individual or entity to whom it is addressed and > may contain information that is confidential, legally privileged, protected > by privacy laws, or otherwise restricted from disclosure to anyone else. If > you are not the intended recipient or the person responsible for delivering > the e-mail to the intended recipient, you are hereby notified that any use, > copying, distributing, dissemination, forwarding, printing, or copying of > this e-mail is strictly prohibited. If you received this e-mail in error, > please return the e-mail to the sender, delete it from your computer, and > destroy any printed copy of it. |
From: HARISH K. I. <har...@gm...> - 2021-10-04 16:51:33
|
Hi Based on this iperf draft document which has been released recently on how to calculate throughput of QUIC (in a pure networking side) Framework for QUIC Throughput Testing (ietf.org) <https://www.ietf.org/id/draft-corre-quic-throughput-testing-00.html#name-measuring-quic-throughput> I believe there is a possible way to introduce quic flag and run it for bidirectional traffic for server and client in order to get more throughput value. Can Iperf developers make this open source and release a solution on this? Thanks BR Harish Kumar |
From: Bob M. <bob...@br...> - 2021-07-05 18:24:30
|
I can't speak for iperf 3 but iperf 2 <https://sourceforge.net/projects/iperf2/>supports -t on the server side. Though I'm not sure if this is what you're wanting as -t will kill the server/listener process and you'll still need to restart it. Bob On Mon, Jul 5, 2021 at 9:02 AM Neil Yeoman <nei...@si...> wrote: > Hi, > > > > I am running Iperf3 (3.7) on a PC (Linux Mint) as the server, with the > client on a development board (Linux). The client connects via LTE (4G), > running a 5 second test every 30 seconds. I am Logging GPS location against > the cellular parameters and the reported Iperf3 throughput measurements. > > > > The problem I am seeing is that if the cellular service is lost during the > test period, the test finishes on the client (–t 5) as expected, but the > following test 30s later cannot re-establish to the server as it still has > the port in use. If we restart the server then all is back to normal. > > > > I am trying to find a timeout command for the server side but it doesn’t > appear to be implemented, can anyone suggest how this problem can be > resolved. I hope I am missing something obvious. > > > > TIA > > > > Neil. > > > > > > P Before printing, please think about the Environment. > > This email message and any accompanying attachments may contain > information which is confidential. If you are not the intended recipient > then you must not read, use, disseminate, distribute or copy this message > or attachments. If you have received this message in error then please > notify the sender immediately and delete this message. Any views expressed > in this message are those of the individual sender except where the sender > expressly, and with authority, expresses them to be the view of Team > Telecom Group Ltd. Before opening any attachments, please check them for > viruses and defects. > > Team Telecom Group Ltd, Field House, Derby, DE1 1NH > > This message has been scanned for viruses & other malicious content > _______________________________________________ > Iperf-users mailing list > Ipe...@li... > https://lists.sourceforge.net/lists/listinfo/iperf-users > -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it. |