From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 09:52:15 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9508916A405 for ; Fri, 26 Jan 2007 09:52:15 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id E600513C483 for ; Fri, 26 Jan 2007 09:52:14 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 26 Jan 2007 09:52:13 -0000 Received: from h081217095052.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.95.52] by mail.gmx.net (mp038) with SMTP; 26 Jan 2007 10:52:13 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: freebsd-current@freebsd.org Date: Fri, 26 Jan 2007 10:52:11 +0100 User-Agent: KMail/1.9.5 References: <20070125.192448.-432840241.imp@bsdimp.com> In-Reply-To: <20070125.192448.-432840241.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701261052.12435.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: "M. Warner Losh" Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 09:52:15 -0000 On Friday 26 January 2007 03:24, M. Warner Losh wrote: > On a lark, I just got a combo USB/Firewire external disk drive. I ran > some crude benchmarks, and I was surprised by what I found. This is > on a fairly stock -current kernel. > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > This is with a simple dd command: On my i386 notebook with USB 2.0 enclosure. Linux: 31.5MB/s FreeBSD: 27.5MB/s There's still room for improvement but numbers don't seem that bad. Maybe you should try knoppix or so to verify it's not the drive's fault. Other than that I'd also guess it's an amd64 problem. Stefan