From owner-freebsd-performance@FreeBSD.ORG Wed May 30 18:25:12 2007 Return-Path: X-Original-To: freebsd-performance@freebsd.org Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 440B916A4D7 for ; Wed, 30 May 2007 18:25:12 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.freebsd.org (Postfix) with ESMTP id 09BF313C469 for ; Wed, 30 May 2007 18:25:11 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.14.0/8.14.0) with ESMTP id l4UIPBqG006966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 May 2007 14:25:11 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id l4UIOhHY036660; Wed, 30 May 2007 14:24:43 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18013.49538.356407.283631@grasshopper.cs.duke.edu> Date: Wed, 30 May 2007 14:24:43 -0400 (EDT) To: security In-Reply-To: <4652383E.9000302@jim-liesl.org> References: <4652383E.9000302@jim-liesl.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: freebsd-performance@freebsd.org Subject: Re: [Fwd: asymetric speeds over gigE link] X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2007 18:25:12 -0000 security writes: > Sent this to -net and didn't get much info, so I'll try here since > there's some overlap > > Summary: Using iperf to measure TCP net speed between a linux (kubuntu edgy) and Iperf is probably your problem, it tends to perform really poorly on nearly any OS other than linux as it measures lots of things besides network performance (like gettimeofday performance). Try a network benchmark that just benchmarks the network, like netperf. For example, on an amd64x2 running -current, I see ~4.75Gb/s from netperf (no options) and 2.85Gb/s from iperf (no options) Drew % netperf242 -H127.0.0.1 TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 127.0.0.1 (127.0.0.1) port 0 AF_INET Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 65536 32768 32768 10.00 4757.03 % iperf -c 127.0.0.1 ------------------------------------------------------------ Client connecting to 127.0.0.1, TCP port 5001 TCP window size: 42.0 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 60961 connected with 127.0.0.1 port 5001 [ 3] 0.0-10.0 sec 3.31 GBytes 2.85 Gbits/sec