Date: Fri, 17 Jun 2005 11:28:46 -0600 (MDT) From: Warner Losh <imp@bsdimp.com> To: jmartin37@speakeasy.net Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD MySQL still WAY slower than Linux Message-ID: <20050617.112846.39214634.imp@bsdimp.com> In-Reply-To: <42B2EC18.3030407@speakeasy.net> References: <005c01c57354$3e877900$fe00a8c0@uzi> <42B2E9B5.7090803@goldsword.com> <42B2EC18.3030407@speakeasy.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. In general, this is true. But since we're in the glide path to a release, and since we have measures in place to keep destablizing commits out of the tree, CURRENT these days isn't a scary place to be if you validate the specific version of current you are deploying. There's risks there, but it isn't like it was at the worst part of the 5.x release cycle where you counted yourself lucky if CURRENT booted on your hardware and was still running the next day... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050617.112846.39214634.imp>