Date: Tue, 24 Oct 2006 18:46:30 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Ronald Klop <ronald-freebsd8@klop.yi.org>, Mike Jakubik <mikej@rogers.com>, stable@freebsd.org Subject: Re: Running large DB's on FreeBSD Message-ID: <20061024084630.GB916@turion.vk2pj.dyndns.org> In-Reply-To: <op.thwglg1v8527sy@guido.klop.ws> References: <453D49D2.1010705@rogers.com> <3861E2E8-4232-4C46-8D0A-1B6079BCA07D@mac.com> <453D53ED.5050403@rogers.com> <5B0599EE-17BE-44E1-8CEC-587FFF1D79C4@mac.com> <op.thwglg1v8527sy@guido.klop.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
--eJnRUKwClWJh1Khz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 2006-Oct-24 02:21:06 +0200, Ronald Klop wrote: >>On Oct 23, 2006, at 4:44 PM, Mike Jakubik wrote: >>>advanced features, but if they are not used, then what is the =20 >>>advantage? (I really like the InnooDB storage in MySQL) One nice thing about MySQL is the plethora of backends - you can pick the backend to suit the type of data and access methods. >Example: writing 1 bit on 1 disk needs to read some info from all disks to= =20 >recalculate the parity. So this doesn't scale very well. Any sane RAID-5 implementation will regenerate the parity by new_parity =3D old_parity XOR old_data XOR new_data Though this still turns a single write into 2 reads and 2 writes. Basically: Don't use RAID-5. --=20 Peter Jeremy --eJnRUKwClWJh1Khz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFPdLm/opHv/APuIcRAgKmAJ9XpzSCUYKmWSUv2wlhixyhXxzpHgCbBTb9 FzYWpqS1EF0lzIBLKAxjdFg= =qr5B -----END PGP SIGNATURE----- --eJnRUKwClWJh1Khz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061024084630.GB916>