On 06/08/16 18:56, h...@symas.com wrote:
> We already have low durability transactions, that's what MDB_NOMETASYNC is
> for. It only does one fsync per commit instead of two.
Haha, I didn't notice that since this reminded me of other discussions.
The stuff I was talking about was for fewer fsyncs
bentr...@comcast.net wrote:
> Full_Name: Ben Trask
> Version:
> OS:
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (192.241.251.11)
>
>
> Hi,
>
> Transaction commits are one of the few bottlenecks in MDB, because it has to
> fsync twice, sequentially.
>
> I think MDB could
On 06. aug. 2016 17:38, bentr...@comcast.net wrote:
> Transaction commits are one of the few bottlenecks in MDB, because it has to
> fsync twice, sequentially.
>
> I think MDB could support mixed low and high durability transactions in the
> same
> database by adding per-page checksums and a
Full_Name: Ben Trask
Version:
OS:
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (192.241.251.11)
Hi,
Transaction commits are one of the few bottlenecks in MDB, because it has to
fsync twice, sequentially.
I think MDB could support mixed low and high durability transactions in
