From: Istvan Marko <notmuch@kismala.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: v4 of DB_RETRY_LOCK patches
Date: Sun, 26 Jun 2016 12:24:56 -0700 [thread overview]
Message-ID: <m3inwvn46v.fsf@zsu.kismala.com> (raw)
In-Reply-To: <1466954985-25761-1-git-send-email-david@tethera.net>
Thanks for getting this into shape, LGTM.
FWIW, I have been running with DB_RETRY_LOCK for the past couple of
months on a fairly large mail spool (500K emails), a high incoming
volume and many tagging rules. So far it's been working great. No
deadlocks, any delays waiting for locks are barely noticeable and it's
so nice not having to deal with those annoying "already locked"
failures.
--
Istvan
next prev parent reply other threads:[~2016-06-26 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 15:29 v4 of DB_RETRY_LOCK patches David Bremner
2016-06-26 15:29 ` [PATCH 1/3] Use the Xapian::DB_RETRY_LOCK flag when available David Bremner
2016-06-29 7:10 ` David Bremner
2016-06-26 15:29 ` [PATCH 2/3] test: initial tests for locking retry David Bremner
2016-06-26 15:29 ` [PATCH 3/3] lib: add built_with handling for XAPIAN_DB_RETRY_LOCK David Bremner
2016-06-26 19:24 ` Istvan Marko [this message]
2016-06-26 20:28 ` v4 of DB_RETRY_LOCK patches Tomi Ollila
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3inwvn46v.fsf@zsu.kismala.com \
--to=notmuch@kismala.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).