Date: Wed, 16 Jun 2004 02:41:48 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: freebsd-current@freebsd.org Subject: Re: Possible Threading problem with -CURRENT / MySQL? Message-ID: <Pine.NEB.3.96L.1040616024014.75630N-100000@fledge.watson.org> In-Reply-To: <Pine.NEB.3.96L.1040616014951.75630L-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Jun 2004, Robert Watson wrote: > On Wed, 16 Jun 2004, Robert Watson wrote: > > > Netperf-UP-giant 4902.41 14.3 > > Netperf-SMP-giant 2566.18 16.83 > > Netperf-UP-mpsafe 4799.35 22.04 > > Netperf-SMP-mpsafe 3022.51 18.06 > > FYI, when I add ADAPTIVE_MUTEXES on this box, the mean of 3000 q/s goes > to 4000 q/s on the netperf+smp+mpsafenet number. > > I'm off to bed now, but it seems like (at least in the HTT > configuration), it makes a big difference. I'll run the remainder of > that set with ADAPTIVE_MUTEXES tomorrow as well. And switching to 4BSD from ULE takes the mean to 6426 q/s when combined with netperf, smp, debug.mpsafenet=1, and adaptive mutexes. (Keeping in mind that this mysql benchmark is basically an inter-thread/process kernel IPC benchmark using UNIX domain sockets, since the workload is fairly minimal in userspace, this makes reasonable sense). Now I'm really going to bed. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040616024014.75630N-100000>