perfsonar-user - Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Brian Candler <>
- To: Tim Rayner <>, Aaron Brown <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3
- Date: Sun, 07 Dec 2014 17:39:00 +0000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type; q=dns; s=sasl; b=Sx/0oWVJ+KYb7+R3y83/FYgjugzAJteH 9AF5E7LoKO2j1aRMlP6o0KalJSbCDRSNCnqGTiubOBA1TAJtfg7EOueIaC84IrI/ dBuzQ3rMwyPFDeaRgxYYEqV2Qj+XAnYo2FMwU/iPNN7ZgwfpcDlwxM2zrZO3Z0kM bFz2jAv9I9Q=
Attached patch bwctl-iperf3.diff.gz adds no_zerocopy option, and with this I get the good performance figures from bwctl. Patch is missing manpage documentation of this option.
During this testing, I was finding problems with bwctl not starting properly - i.e. getting empty test results (example below). Restarting bwctld generally seemed to fix it.
Possibly there is some problem with uninitialised variables. I know that my clocks are not properly NTP synced, but they have been reset with "ntpdate -u" and are pretty close to each other.
Regards,
Brian.
$ bwctl -x -v -a 2 -c cov-perf-1 -T iperf3
Messages being sent to syslog(user,err)
bwctl: NTP: Status UNSYNC (clock offset problems likely)
bwctl: Using 192.0.2.251 as the address for local sender
bwctl: Using cov-perf-1 as the address for remote receiver
bwctl: Available in-common: iperf nuttcp iperf3
bwctl: Using tool: iperf3
bwctl: Server 'cov-perf-1' accepted test request at time 1417973274.403474
bwctl: Client 'localhost' accepted test request at time 1417973274.403474
bwctl: 15 seconds until test results available
RECEIVER START
bwctl: start_endpoint: 3626962070.002842
bwctl: run_endpoint: receiver: 192.0.2.254
bwctl: run_endpoint: sender: 192.0.2.251
bwctl: run_tool: tester: iperf3
bwctl: run_tool: receiver: 192.0.2.254
bwctl: run_tool: sender: 192.0.2.251
bwctl: start_tool: 3626962072.702455
iperf 3.0.9
Linux cov-perf-1.network.example.com 2.6.32-504.1.3.el6.aufs.web100.x86_64 #1 SMP Wed Nov 12 16:01:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
iperf3: interrupt - the server has terminated
-----------------------------------------------------------
Server listening on 5872
-----------------------------------------------------------
bwctl: remote peer cancelled test
bwctl: stop_tool: 3626962076.407806
bwctl: stop_endpoint: 3626962076.408613
RECEIVER END
SENDER START
bwctl: start_endpoint: 3626962070.004077
bwctl: run_endpoint: receiver: 192.0.2.254
bwctl: run_endpoint: sender: 192.0.2.251
bwctl: run_tool: tester: iperf3
bwctl: run_tool: receiver: 192.0.2.254
bwctl: run_tool: sender: 192.0.2.251
bwctl: start_tool: 3626962074.403644
iperf 3.0.9
Linux bou-perf-1.network.example.com 2.6.32-504.1.3.el6.aufs.web100.x86_64 #1 SMP Wed Nov 12 16:01:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
bwctl: stop_tool: 3626962074.408072
bwctl: stop_endpoint: 3626962076.409385
SENDER END
$ bwctl -x -v -a 2 -c cov-perf-1 -T iperf3
Messages being sent to syslog(user,err)
bwctl: NTP: Status UNSYNC (clock offset problems likely)
bwctl: Using 192.0.2.251 as the address for local sender
bwctl: Using cov-perf-1 as the address for remote receiver
bwctl: Available in-common: iperf nuttcp iperf3
bwctl: Using tool: iperf3
bwctl: Server 'cov-perf-1' accepted test request at time 1417973274.403474
bwctl: Client 'localhost' accepted test request at time 1417973274.403474
bwctl: 15 seconds until test results available
RECEIVER START
bwctl: start_endpoint: 3626962070.002842
bwctl: run_endpoint: receiver: 192.0.2.254
bwctl: run_endpoint: sender: 192.0.2.251
bwctl: run_tool: tester: iperf3
bwctl: run_tool: receiver: 192.0.2.254
bwctl: run_tool: sender: 192.0.2.251
bwctl: start_tool: 3626962072.702455
iperf 3.0.9
Linux cov-perf-1.network.example.com 2.6.32-504.1.3.el6.aufs.web100.x86_64 #1 SMP Wed Nov 12 16:01:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
iperf3: interrupt - the server has terminated
-----------------------------------------------------------
Server listening on 5872
-----------------------------------------------------------
bwctl: remote peer cancelled test
bwctl: stop_tool: 3626962076.407806
bwctl: stop_endpoint: 3626962076.408613
RECEIVER END
SENDER START
bwctl: start_endpoint: 3626962070.004077
bwctl: run_endpoint: receiver: 192.0.2.254
bwctl: run_endpoint: sender: 192.0.2.251
bwctl: run_tool: tester: iperf3
bwctl: run_tool: receiver: 192.0.2.254
bwctl: run_tool: sender: 192.0.2.251
bwctl: start_tool: 3626962074.403644
iperf 3.0.9
Linux bou-perf-1.network.example.com 2.6.32-504.1.3.el6.aufs.web100.x86_64 #1 SMP Wed Nov 12 16:01:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
bwctl: stop_tool: 3626962074.408072
bwctl: stop_endpoint: 3626962076.409385
SENDER END
Attachment:
bwctl-iperf3.diff.gz
Description: application/gzip
- [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/04/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Tierney, 12/04/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/04/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Aaron Brown, 12/05/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/05/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/05/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/05/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/06/2014
- RE: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Tim Rayner, 12/06/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/07/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/07/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Aaron Brown, 12/09/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/09/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/09/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Aaron Brown, 12/10/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/10/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/11/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Aaron Brown, 12/11/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/11/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/07/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/07/2014
- RE: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Tim Rayner, 12/06/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/10/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/11/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/06/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Candler, 12/05/2014
- Re: [perfsonar-user] Different results from iperf3 vs. bwctl -T iperf3, Brian Tierney, 12/04/2014
Archive powered by MHonArc 2.6.16.