I'm confused.
We're in the middle of a discussion on the user list about
performance, I'm told in no uncertain terms that this extreme level of
commit is absolutely required to avoid db corruption because no one
can control what the Erlang VM does (or something...) and without a
word of discussion on the dev list, the behavior is changed?
Doesn't something like this at least warrant a "head up" kind of mail
to the dev list? How does it work? How can I control the
asynchronicity?
geir
On Jan 5, 2009, at 3:58 AM, Jason Davies wrote:
On 5 Jan 2009, at 08:51, Alan Bell wrote:
I just upgraded to the SVN code and it got nearly 5 times faster on
inserting empty documents I am now up to 390/second on the same
hardware that got 80/second before. This machine does recreate_doc
in 365ms in the test suite.
I'm assuming the speedup you are seeing is due to the "delayed
commit" stuff Damien committed in r731452. Apparently documents are
now committed asynchronously by default.
--
Jason Davies
www.jasondavies.com
