Also, for UDP you need to pass the –u option for the server as well. (This
isn’t the case for iperf3 though, just iperf v2)
From: Bob (Robert) McMahon [mailto:rmcma...@broadcom.com]
Sent: Friday, March 13, 2015 11:44 AM
To: onkar kundargi; iperf-users@lists.sourceforge.net
Subject: Re: [Iperf-users] Fwd: input to consider for jitter and throughput
Sorry, not sure I understand the question. To control throughput use –b on
the client. Jitter isn’t an input but is a measure value on the server. You
have to use UDP packets to get jitter measurements. Use –u for that.
Something like
iperf –c <dest> -b 1G –u
Bob
From: onkar kundargi [mailto:onkar.kunda...@gmail.com]
Sent: Friday, March 13, 2015 2:47 AM
To: iperf-users@lists.sourceforge.net<mailto:iperf-users@lists.sourceforge.net>
Subject: [Iperf-users] Fwd: input to consider for jitter and throughput
Hello ,
May i know command to consider throughput as input and also jitter
as input
thanks
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Iperf-users mailing list
Iperf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/iperf-users