Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Dec 2007 15:08:28 +0100
From:      Kris Kennaway <kris@FreeBSD.org>
To:        Gergely CZUCZY <phoemix@harmless.hu>
Cc:        Jeff Roberson <jroberson@chesapeake.net>, freebsd-performance@freebsd.org
Subject:   Re: mysql scaling questions
Message-ID:  <4777A65C.8020406@FreeBSD.org>
In-Reply-To: <20071230134354.GA63555@harmless.hu>
References:  <20071201163334.GA21709@harmless.hu> <200712012055.lB1Kt5IQ005728@lava.sentex.ca> <20071201205609.GA54238@harmless.hu> <200712012108.lB1L8qAd005766@lava.sentex.ca> <20071201211012.GA55519@harmless.hu> <20071201122122.S884@192.168.1.107> <20071204130810.GA77186@harmless.hu> <47779AA7.2060801@FreeBSD.org> <20071230132451.GA61295@harmless.hu> <47779EBC.5020900@FreeBSD.org> <20071230134354.GA63555@harmless.hu>

next in thread | previous in thread | raw e-mail | index | archive | help
Gergely CZUCZY wrote:
> On Sun, Dec 30, 2007 at 02:35:56PM +0100, Kris Kennaway wrote:
>> Gergely CZUCZY wrote:
>>
>>>> I appreciate that you might be constrained by local requirements, but it's really not meaningful to compare different mysql versions 
>>>> if your goal is to study OS performance.
>>> It'd be a PITA to install the both versions. Maybe now, that the ports freeze is over, i can
>>> do something. But honestly, every mysql version was faster on linux, than eny on FreeBSD,
>>> even the .22 one was faster. We start work on Jan02, I will see what can I do.
>> Regardless, we need a stable baseline to compare to.
> Cannot do it sooner then january. Any recommended versions?

Either 5.0.45 on both, or 5.0.51 on both, please.

>> Still waiting for your sysbench command lines :)
> There were 2 scripts and a sources file with options:
> 
> basicall that's everything. I know it's a but complex, but this was all behind it.

OK, that was very important since you're changing defaults.

It looks like myisam is doing huge numbers of concurrent reads of the 
same file which is running into exclusive locking in the kernel (vnode 
interlock and lockbuilder mtxpool).  Does it not do any caching of the 
data in userspace but relies on querying into the kernel every time? 
innodb doesn't have this behaviour.

Kris




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4777A65C.8020406>