[Date Prev][Date Next]
Re: MDB, read/write mmap
- To: Howard Chu <firstname.lastname@example.org>
- Subject: Re: MDB, read/write mmap
- From: Nikolaos Milas <email@example.com>
- Date: Wed, 05 Sep 2012 11:11:31 +0300
- Cc: "OpenLDAPfirstname.lastname@example.org" <OpenLDAPemail@example.com>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=noa.gr; s=default; t=1346832686; bh=BVQJMjZdaHZPDmnlF2aPCuM7cbRCiS7QrhoIJXVadpg=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=E60njOLM6/RLBWGqw/cupWBUU15XrYahSDxe139Sxu87Fmxsajry9117k7D/QQVm7 1OM2pVa0NCKNlvh+UEY0McvKSyf70T32c0/GeBLiziqvtyU7/LP3Jj27mOK+xn+33Z i6lTRZfDanlD6h86wjEsPyQx6f38qGtnYSlLVxDU=
- In-reply-to: <50460CD0.firstname.lastname@example.org>
- Organization: National Observatory of Athens
- References: <50460CD0.email@example.com>
- User-agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
On 4/9/2012 5:14 ÎÎ, Howard Chu wrote:
It seems to me this can only be a viable mode of operation if you're always
going to run asynch and don't care much about transaction durability or DB
recoverability. Running in this mode offers absolutely zero crash resistance;
the entire DB will almost always be irreparably damaged after a system crash.
Would you run like that, if it offered you the potential of maybe 10x faster
Absolutely not! DB reliability is crucial to us. Transaction durability
too, esp. since we are using syncrepl in refreshAndPersist mode and
numerous production systems (consumers) are affected.
Thanks for asking!