From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] modulo the file size in a maildir, so it's <= 7 digits.
Date: Thu, 24 Jan 2008 21:14:01 -0800 [thread overview]
Message-ID: <1201237734-sup-3305@south> (raw)
In-Reply-To: <1201081580-sup-6798@tomsk>
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 <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-25 5:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 8:58 Jeff Balogh
2008-01-22 3:03 ` William Morgan
2008-01-22 14:01 ` Jeff Balogh
2008-01-23 5:20 ` William Morgan
2008-01-22 20:44 ` Marcus Williams
2008-01-23 5:20 ` William Morgan
2008-01-23 9:59 ` Marcus Williams
2008-01-25 5:14 ` William Morgan [this message]
2008-01-27 20:07 ` Marcus Williams
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=1201237734-sup-3305@south \
--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