From owner-freebsd-threads@FreeBSD.ORG Sat May 22 13:56:04 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7742A16A4CE for ; Sat, 22 May 2004 13:56:04 -0700 (PDT) Received: from ojoink.com (center.ojoink.com [216.65.123.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58CF043D2D for ; Sat, 22 May 2004 13:56:04 -0700 (PDT) (envelope-from amd64list@jpgsworld.com) Received: (qmail 15734 invoked by uid 89); 22 May 2004 21:00:26 -0000 Received: from unknown (HELO MAINBX.jpgsworld.com) (amd64list@jpgsworld.com@24.10.96.33) by center.ojoink.com with SMTP; 22 May 2004 21:00:26 -0000 Message-Id: <5.2.0.9.2.20040522135338.0158cc50@mail.ojoink.com> X-Sender: amd64list@jpgsworld.com@mail.ojoink.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sat, 22 May 2004 13:56:05 -0700 To: freebsd-threads@freebsd.org From: JG In-Reply-To: <40AF9259.9010204@he.iki.fi> References: <5.2.0.9.2.20040522100318.01598f50@mail.ojoink.com> <5.2.0.9.2.20040522052606.0156fd70@mail.ojoink.com> <5.2.0.9.2.20040521154458.01627688@127.0.0.1> <5.2.0.9.2.20040521154458.01627688@127.0.0.1> <5.2.0.9.2.20040522052606.0156fd70@mail.ojoink.com> <5.2.0.9.2.20040522100318.01598f50@mail.ojoink.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: Why is MySQL nearly twice as fast on Linux? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 May 2004 20:56:04 -0000 At 08:48 PM 5/22/2004 +0300, you wrote: >JG wrote: > >> >>>It would be interesting if mysql is cpu-bound or disk bound in your >>>tests and if disk-bound >> >> >> >>Anyway, I would be happy to do some disk I/O benchmarks as well. >> >>What program would you suggest for testing on both OS's ? >I was more suggesting toward running gstat when the mysql benchmark is >running. > >Pete While the benchmarks are running, gstat basically looks like this: amd64f# gstat dT: 0.502 flag_I 500000us sizeof 288 i -1 L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 0 0 0 0 0.0 0 0 0.0 0.0| ad0 0 0 0 0 0.0 0 0 0.0 0.0| ad0s1 0 0 0 0 0.0 0 0 0.0 0.0| acd0 0 0 0 0 0.0 0 0 0.0 0.0| amrd0 0 0 0 0 0.0 0 0 0.0 0.0| amrd1 0 0 0 0 0.0 0 0 0.0 0.0| ad0s1a 0 0 0 0 0.0 0 0 0.0 0.0| ad0s1b 0 0 0 0 0.0 0 0 0.0 0.0| ad0s1c 0 0 0 0 0.0 0 0 0.0 0.0| ad0s1d 0 0 0 0 0.0 0 0 0.0 0.0| ad0s1e 0 0 0 0 0.0 0 0 0.0 0.0| amrd0s1 0 0 0 0 0.0 0 0 0.0 0.0| amrd1s1 With the exception of a few split-second ticks to the amrd1 drive (the mysql data drive)