Chris Elsworth wrote:
Forenote: I have no wish to start an OS debate.

Hello,

I'm in the fortunate position of having a dual 2.8GHz Xeon with 4G of
ram and 4 10k SCSI disks (configured in RAID-10) to deploy as a new
MySQL server.

Since I'm a numbers freak, I've been running super-smack on it for the
last few days to see how it stacks up.

Tweaking various configs and kernel options, on any OS, obviously wins
a few hundred/thousand queries per second, but I'm really quite
surprised at one major difference.

Optimisations and tweaking aside, FreeBSD 5.2.1-p6 on this hardware
did well to achieve 17,000 queries per second, using super-smack's
select-key.smack with the query cache turned on. Nothing I could do,
and I spent days trying, got it much higher.

Once I wiped this and tried Linux (both gentoo, with their
patched-to-the-hilt 2.6.5 kernel, and Debian, with a stock 2.6.6 which
had just been released by the time I installed) this figure jumped to
35,000 queries per second.

Is FreeBSD really this crap for MySQL? I was quite horrified. FreeBSD
5 has a number of threading libraries, and I tried them all.
LinuxThreads won (slightly, there wasn't much in it). I'm very much a
FreeBSD fan and I'd quite like to keep FreeBSD on this machine before
it goes live, but the performance pales in comparison to Linux.

I had to do absolutely no tweaking to achieve 35,000 queries/sec in
Linux.

Has anyone else observed similar behaviour? Does anyone else have
similar hardware with FreeBSD on? Have you fared any better?

Thanks for any comments,

Chris:

It looks like FreeBSD was using only one CPU from your numbers. Try the test with only 1 thread and a lot of iterations to avoid the influence of overhead. I know very little about FreeBSD, but one thing I would check is if the kernel was configured to be SMP-cabaple/enabled.


-- Sasha Pachev Create online surveys at http://www.surveyz.com/

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to