From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] xapian question
Date: Mon, 03 Aug 2009 11:03:54 -0700 [thread overview]
Message-ID: <1249320789-sup-2608@masanjin.net> (raw)
In-Reply-To: <1249098509-sup-6664@pion.club.cc.cmu.edu>
Reformatted excerpts from Rich Lane's message of 2009-07-31:
> I tried out using add_term/remove_term for immediate label changes.
> It's significantly faster than sync_message,
Excellent.
> but it still makes the interface feel laggy. There's known room for
> improvement in Xapian's replace_document. However, we'll still have a
> lot of latency when we start using remote sup-servers, so I don't
> think it's a good idea to do these index operations synchronously with
> the UI.
I agree, synchronous is not an option.
> We could queue up index writes and execute them in a background
> thread. We'd want label additions to show up immediately in a search,
> though. This is easy to do for inbox-mode and label-view-mode, which
> covers most of my daily usage.
I'm fine with queuing up index writes and letting the user continue
while they take effect in the background. I'm also fine with the easier
option of just blocking during a search until the writes are complete.
> If/when we support multiple clients connecting to a sup-server, we'll
> need a way to notify them that someone else modified a message.
I think this is more of a nice-to-have than a necessity, but it would be
nice to have, even if it was a "we've detected a change somewhere on the
internet; reload? (y/n)"-kinda thing.
> How is sup-server development going?
Well. I have a simple version that stores "items" to files on disk, and
uses Ferret to provide the search semantics. It's modular enough that
upgrading to Xapian shouldn't be as painful as it was with Sup. There
are even unit tests that enforce the semantics of the modules. Go me.
I'm going to make a couple internal API changes in Sup and then try
throwing the code together.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-08-03 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:45 William Morgan
2009-07-28 15:57 ` Rich Lane
2009-07-28 19:05 ` William Morgan
2009-08-01 6:28 ` Rich Lane
2009-08-03 18:03 ` William Morgan [this message]
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=1249320789-sup-2608@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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