Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] [PATCH] xapian: do less work for update_message_state
Date: Thu, 01 Oct 2009 13:02:18 -0400	[thread overview]
Message-ID: <1254416360-sup-8957@zyrg.net> (raw)
In-Reply-To: <1254404707-sup-9253@masanjin.net>

Excerpts from William Morgan's message of Thu Oct 01 09:46:20 -0400 2009:
> Reformatted excerpts from Rich Lane's message of 2009-09-30:
> > They're about 3 times faster on my machine with this patch. An
> > optimization the Xapian devs have been planning to make (and that this
> > patch is necessary to take advantage of) should increase performance
> > much more.
> 
> Awesome. Out of curiousity, what's the optimization?

replace_document currently deletes all the old postings and inserts new
ones. It can be optimized to make the minimal set of modifications.


  reply	other threads:[~2009-10-01 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-13 18:44 Rich Lane
2009-09-30 19:40 ` William Morgan
2009-09-30 20:16   ` Rich Lane
2009-10-01 13:46     ` William Morgan
2009-10-01 17:02       ` Rich Lane [this message]
2009-10-02  7:57         ` Olly Betts
2010-02-04  3:42           ` Olly Betts
2010-02-18  2:27             ` Olly Betts

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1254416360-sup-8957@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox