Date: Fri, 17 Jun 2005 12:05:54 -0400 From: JM <jmartin37@speakeasy.net> To: David Sze <dsze@distrust.net> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD MySQL still WAY slower than Linux Message-ID: <42B2F4E2.4000507@speakeasy.net> In-Reply-To: <20050617154149.GA94284@mail.distrust.net> References: <6.2.1.2.2.20050617103807.058c6fa8@mail.distrust.net> <005c01c57354$3e877900$fe00a8c0@uzi> <42B2E9B5.7090803@goldsword.com> <42B2EC18.3030407@speakeasy.net> <20050617154149.GA94284@mail.distrust.net>
next in thread | previous in thread | raw e-mail | index | archive | help
David Sze wrote: >On Fri, Jun 17, 2005 at 11:28:24AM -0400, JM wrote: > > >>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. >> >> > >Under normal circumstances I'd agree, but -CURRENT is already in code >freeze in preparation for the upcoming 6.0 release: > > http://www.freebsd.org/releases/6.0R/schedule.html > >I also follow the cvs-src mailing list pretty closely, and I like the >stability and performance increases that have gone into there. It seems >like most of them won't be backported to RELENG_5 because they break ABI >compatibility. > > > > code freeze != glitch free XD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42B2F4E2.4000507>