unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Austin Clements <amdragon@MIT.EDU>
To: notmuch@notmuchmail.org
Subject: [PATCH 0/5] Fetch all message metadata in a single pass
Date: Thu,  9 Dec 2010 15:59:51 -0500	[thread overview]
Message-ID: <1291928396-27937-1-git-send-email-amdragon@mit.edu> (raw)

This is the second of the two optimizations I described a while ago,
and brings my inbox search down to 1.811 seconds, 2.5X faster than it
was originally.

This optimization is based on the observation that Xapian decompresses
a document's term list every time you iterate over it.  As a result,
notmuch can decompress the beginning of a single term list quite a few
times.  This patch series combines all of this into a single pass that
is only slightly more expensive than fetching one metadata field used
to be, but offers a huge win in the common case where a message object
is used for multiple metadata fields.

             reply	other threads:[~2010-12-09 21:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 20:59 Austin Clements [this message]
2010-12-09 20:59 ` [PATCH 1/5] Use a single unified pass to fetch scalar message metadata Austin Clements
2010-12-09 20:59 ` [PATCH 2/5] Implement an internal generic string list and use it Austin Clements
2010-12-23  2:44   ` Austin Clements
2010-12-09 20:59 ` [PATCH 3/5] Add a generic function to get a list of terms with some prefix Austin Clements
2010-12-09 20:59 ` [PATCH 4/5] Add the file name list to the unified message metadata pass Austin Clements
2010-12-09 20:59 ` [PATCH 5/5] Add the tag " Austin Clements
2011-02-13 20:25 ` [PATCH 0/5] Fetch all message metadata in a single pass Austin Clements
2011-03-11  3:48   ` Carl Worth
2011-03-21  6:56     ` Austin Clements
2011-04-25 20:52       ` Carl Worth
2011-04-25 21:42         ` Carl Worth

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=1291928396-27937-1-git-send-email-amdragon@mit.edu \
    --to=amdragon@mit.edu \
    --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).