[Date Prev][Date Next]
Re: [WIP] WiredTiger Backend
- To: Howard Chu <firstname.lastname@example.org>
- Subject: Re: [WIP] WiredTiger Backend
- From: HAMANO Tsukasa <email@example.com>
- Date: Mon, 27 Apr 2015 14:02:37 +0900
- Cc: firstname.lastname@example.org, HAMANO Tsukasa <email@example.com>
- In-reply-to: <553DB104.firstname.lastname@example.org>
- References: <email@example.com> <553DB104.firstname.lastname@example.org>
- User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.4 (x86_64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO)
Thanks for your responce!
On 月, 27 4月 2015 at 12:46:12 JST,
Howard Chu wrote:
> Interesting, thanks for the contribution. Looks like there is no
> manpage though, do you have one?
I will write it soon :p
> > Some note:
> > * slapadd, slapcat, slapindex will works.
> > * LDAP BIND, ADD, DELETE, SEARCH will works.
> How well does it work, good enough to run benchmarks now?
I have just tested on virtual machine, back-wt LDAP ADD(with single
thread) is 20-30x times faster than back-bdb.
I'm looking forward to benchmarking with many thread.
I'll publish benchmarks just when I get high spec machine.
> > * WiredTiger is not support multiprocess access yet.
> > It mean that we can't to do slatcat while running slapd.
> > It will be supported in the future.
> You should use alock in the meantime then, to prevent multiprocess access.
WiredTiger is planning to implement RPC for multiprocess access.
I think it will communicate with unix domain socket.
I'm planning to use the feature to avoid multi process locking.
Open Source Solution Technology Corporation
HAMANO Tsukasa <email@example.com>
fingerprint = 2285 2111 6D34 3816 3C2E A5B9 16BE D101 6069 BE55