From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] header cache
Date: Tue, 22 Jan 2008 09:40:05 +0100 [thread overview]
Message-ID: <1200990925-sup-1529@ausone.local> (raw)
In-Reply-To: <1200969359-sup-2816@south>
Excerpts from William Morgan's message of Tue Jan 22 03:36:48 +0100 2008:
> Reformatted excerpts from nicolas.pouillard's message of 2008-01-17:
> > That's because Sup needs to compute a hash from file names to message
> > ids.
>
> Like IMAP headers, this is a one-time cost upon startup and could easily
> be cached. Maildir shouldn't be significantly slower than mbox except
> for this.
Looking at the code 'scan_mailbox' seems to be called quite often (but not
more than every 30 seconds).
I'm wondering if peeking a file in a very large directory is as fast as
seeking to a particular offset in a large file?
--
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080122/41112479/attachment.bin
next prev parent reply other threads:[~2008-01-22 8:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 12:54 Giorgio Lando
2008-01-16 3:24 ` William Morgan
2008-01-16 20:26 ` Giorgio Lando
2008-01-16 20:48 ` William Morgan
2008-01-16 22:04 ` Giorgio Lando
2008-01-16 22:58 ` Alec Berryman
2008-01-16 23:36 ` Giorgio Lando
2008-01-17 8:13 ` Nicolas Pouillard
2008-01-17 11:40 ` Giorgio Lando
2008-01-17 14:56 ` Nicolas Pouillard
2008-01-22 2:36 ` William Morgan
2008-01-22 8:40 ` Nicolas Pouillard [this message]
2008-01-23 20:33 ` Gabriel Sean Farrell
[not found] ` <1201071069-sup-6394@south>
[not found] ` <1201079068-sup-438@ausone.inria.fr>
2008-01-25 3:28 ` William Morgan
2008-01-25 8:50 ` Nicolas Pouillard
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=1200990925-sup-1529@ausone.local \
--to=nicolas.pouillard@gmail.com \
/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