Reformatted excerpts from Marcus Williams's message of 2008-01-23: > If you store the id in the ferret index, is it quick enough just to > use ferret to tell you if its there? That way an id could be a string > and could be tracked by the source via ferret (a source would just > have to guarantee its unique when combined with the source id).
I don't think so. I haven't tested this empirically, and Ferret is pretty darn fast, but it comes down to this: if we have to perform an operation a number of times that scales linearly with the number of messages in a mailstore (which unfortunately we do), that operation shouldn't be something like "do a search on a search engine". In fact, if the make_id call /is/ actually slower than a Ferret search, and that's the bottleneck, we can rewrite that with RubyInline or something and there's no way Ferret will be faster than that. > Off on a slight tangent - I cant get any maildir working with sup > here. I added a maildir to my sources list and it gets scanned as > expected but nothing gets into the index. I'm wondering whether this > is as a result of the id function. Is this with Jeff's fix for the id? -- William <[EMAIL PROTECTED]> _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
