From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] Writing time-sensitive portions of sup in C
Date: Thu, 01 Oct 2009 11:41:59 -0700 [thread overview]
Message-ID: <1254421959-sup-9506@yoom.home.cworth.org> (raw)
In-Reply-To: <1254418089-sup-5800@ben-laptop>
Excerpts from Ben Gamari's message of Thu Oct 01 10:44:19 -0700 2009:
> Excerpts from William Morgan's message of Thu Oct 01 09:43:48 -0400 2009:
> > Here's the idea: scanning over a mailstore is slow. Much of this
> > slowness is due to Ruby. So let's rewrite this code in C. Then we would
> > have something as fast as, say, Mutt. But Mutt bogs down on my mbox file
> > because it's too big. So my *only* reasonable choice with a large
> > mailstore is Sup and the assumption that the source is add only.
>
> It seems that C would definitely be a good start (or perhaps C++ would
> be a better idea as that is the language in which Xapian is written).
I've started some experiments along these lines, (basically just
writing C code (with C++ where necessary) using the Xapian tutorial
and little peeks into sup/xapian-index.rb to get the right prefix
values, etc.).
> However, I think one of the real issues is the exclusive nature of index
> access. In fact, this is one of my primary gripes with the sup
> workflow. After processing a large number of messages, the write-out
> time can be quite substantial upon killing the buffer. This can be a
> noticeable interruption to workflow. It seems to me that index access
> should be asynchronous at least.
What I'm hoping to end up with is a C library that provides
asynchronous access to a sup-compatible index. I'll keep you posted if
I make any actual progress on this front.
-Carl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20091001/89e0a628/attachment.bin>
next prev parent reply other threads:[~2009-10-01 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 16:58 [sup-talk] Crash while scrolling Ben Gamari
2009-09-12 16:35 ` William Morgan
2009-09-13 15:02 ` Ben Gamari
2009-09-16 17:23 ` Ben Gamari
2009-09-26 14:31 ` William Morgan
2009-09-28 18:10 ` Ben Gamari
2009-10-01 13:43 ` William Morgan
2009-10-01 17:44 ` Ben Gamari
2009-10-01 18:31 ` William Morgan
2009-10-01 19:01 ` Ben Gamari
2009-10-11 20:31 ` William Morgan
2009-10-01 18:41 ` Carl Worth [this message]
2009-09-30 21:21 ` William Morgan
2009-10-04 19:59 ` Guillaume Quintard
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=1254421959-sup-9506@yoom.home.cworth.org \
--to=cworth@cworth.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox