From owner-freebsd-threads@FreeBSD.ORG Sun May 23 04:33:02 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 E9D5D16A4CF for ; Sun, 23 May 2004 04:33:01 -0700 (PDT) Received: from rms04.rommon.net (rms04.rommon.net [212.54.2.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id E87D643D2D for ; Sun, 23 May 2004 04:33:00 -0700 (PDT) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h91.vuokselantie10.fi [193.64.42.145]) by rms04.rommon.net (8.12.10/8.12.9) with ESMTP id i4NBWe3v026661; Sun, 23 May 2004 14:32:41 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <40B08BD8.4030004@he.iki.fi> Date: Sun, 23 May 2004 14:32:40 +0300 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: JG 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> <5.2.0.9.2.20040522135338.0158cc50@mail.ojoink.com> In-Reply-To: <5.2.0.9.2.20040522135338.0158cc50@mail.ojoink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-threads@freebsd.org 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: Sun, 23 May 2004 11:33:02 -0000 JG wrote: > > 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) > Which means that either your dataset fits into the memory you have allocated for mysql or your are CPU bound or both. How does top -H look when running the test? Pete