Date: Mon, 20 Jun 2005 02:29:46 -0500 From: "Jim C. Nasby" <decibel@decibel.org> To: Greg Barniskis <nalists@scls.lib.wi.us> Cc: uzi@bmby.com, freebsd-stable@freebsd.org Subject: Re: FreeBSD MySQL still WAY slower than Linux Message-ID: <20050620072946.GL5113@decibel.org> In-Reply-To: <42B2EC91.8070800@scls.lib.wi.us> References: <6.2.1.2.2.20050617103807.058c6fa8@mail.distrust.net> <005c01c57354$3e877900$fe00a8c0@uzi> <42B2E9B5.7090803@goldsword.com> <42B2EC91.8070800@scls.lib.wi.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 17, 2005 at 10:30:25AM -0500, Greg Barniskis wrote: > I think he meant comparing 36,000 on CentOS (async) to 24,000 on > CURRENT (sync). I wondered that myself, and having searched out the > answer I find that it is declared in > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-disk.html > > that async provides fast writes at the cost of "no guarantee at all > for a consistent state of the filesystem". So, you choose: fast but > not so reliable writes, or slower writes with fast, reliable > disaster recovery. > > Thanks to the FreeBSD team for choosing the sensible default, even > if it results in the occasional "Linux is faster!" debate. Dang > smirky penguins... you're flightless I tell ya, flightless. =) Note that it's very easy to accidentally configure MySQL in such a manner that you don't have any data integrity anyway. For example, if you fat-finger 'innodb' as 'innodd' or something MySQL siletly creates a MyISAM table for you. So if you care about data integrity, you should probably look beyond MySQL in the first place. -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050620072946.GL5113>