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
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
