J. T. Farmer wrote:
Uzi wrote:
[...]
super-smack select-key
5.4-RELEASE ~20,000 queries/second
6.0-CURRENT ~24,000 queries/second
CentOS w/async ~36,000 queries/second
CentOS w/sync ~26,000 queries/second
super-smack update-select
5.4-RELEASE ~4,000 queries/second
6.0-CURRENT ~4,500 queries/second
CentOS w/async ~7,500 queries/second
CentOS w/sync ~750 queries/second
That last CentOS number is not a typo, it was an order of magnitude
slower. I didn't try other file systems on CentOS, just the default
ext3. It's possible that reiserfs or xfs might not be as affected by
switching from async to sync.
So my production server is now happily running mysql 4.1 on
6.0-CURRENT :).
I don't get it.
You get 30% less perfomance, running a non-production release for
production, and happy about it?
Try reading it again. The last time I checked, 24k queries/sec _is_
faster than
20k queries/sec. And 4.5k queries/sec is faster than 4.0k queries/sec.
John
i think you're missing the point... using CURRENT on a production
machine is a bad idea... the performance is great, but hardly worth the
risk of breaking something.
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
