Date: Fri, 17 Jun 2005 20:11:58 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: David Sze <dsze@distrust.net> Cc: freebsd-stable@freebsd.org, nalists@scls.lib.wi.us, uzi@bmby.com, mkb@incubus.de Subject: Re: FreeBSD MySQL still WAY slower than Linux Message-ID: <20050617201158.00ec8646.steve@sohara.org> In-Reply-To: <20050617185726.GD94284@mail.distrust.net> References: <20050617155938.GB94284@mail.distrust.net> <200506171620.j5HGKxwW042819@drjekyll.mkbuelow.net> <20050617185726.GD94284@mail.distrust.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 Jun 2005 13:57:26 -0500
David Sze <dsze@distrust.net> wrote:
> I'm not sure filesystem consistency alone is "good enough". Say your
> bank's database crashes right after you make a deposit. When it comes
> back up it's consistent, but only up to 5 minutes before the crash due
> to the async mount.
>
> For this type of application, something in the system has to be keeping
> a "journal" on a sync mount in order for recovery to be both consistent
> and correct.
For that critical an application the transaction should be stored
in multiple physically separated locations and confirmed by the two faced
kermit\w\w\w two phase commit protocol. Said implementation had better have
the correct disaster restart protocol implemented too.
--
C:>WIN | Directable Mirror Arrays
The computer obeys and wins. | A better way to focus the sun
You lose and Bill collects. | licences available see
| http://www.sohara.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050617201158.00ec8646.steve>