From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] header cache
Date: Fri, 25 Jan 2008 09:50:20 +0100 [thread overview]
Message-ID: <1201250434-sup-4567@ausone.local> (raw)
In-Reply-To: <1201230428-sup-8760@south>
Excerpts from William Morgan's message of Fri Jan 25 04:28:07 +0100 2008:
> [Sending to list. We accidentally fell off.]
>
> Reformatted excerpts from nicolas.pouillard's message of 2008-01-23:
> > Excerpts from William Morgan's message of Wed Jan 23 08:04:27 +0100 2008:
> > > Reformatted excerpts from nicolas.pouillard's message of 2008-01-22:
> > > > Looking at the code 'scan_mailbox' seems to be called quite
> > > > often (but not more than every 30 seconds).
> > >
> > > Oops, you're exactly right.
> > >
> > > > 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?
> > >
> > > Actually, we could short-circuit this check trivially by comparing
> > > the directories' mtimes. Then this really shouldn't be a slowdown.
> >
> > You will still scan it at when receiving new mails...
>
> That's true. But some kind of scan is unavoidable. We need to know which
> files are new, and one way or another that will involve pulling in the
> whole list of files.
>
> I think we can do a couple easy things to speed up Maildir dramatically.
> Skip the scan when the mtime is unchanged, maybe increase the delay,
> stop repeating make_id calls for messages we've already processed...
> basically the current implementation is a little naive and I'm not ready
> to give up on Maildir quite yet.
What about having two directories? new and cur for instance :)
You always have to scan new and move them to cur when they are in the index.
> > What about having a custom mail box format for sup?
> >
> > For instance I think the only drawback (in the context of using sup)
> > of mbox is when you often backup you mails. Why not having a bunch of
> > mbox using dates inbox-12-2008.mbox? Or a directory where file names
> > are sup message ids?
>
> What about mbox makes it difficult to do backups?
Every hour, if my backup drive is plugged in, my OS make a new tree of my
entire disk by hard linking what's haven't change and by coping others.
However this behave particularly bad with files that just keep growing every
hour ~400MB at this day.
That's why splitting out my big mail box in small ones, let's say every
month, would better behave w.r.t. to backups.
> The amount of work for a custom format seems really high. (Look at all
> the design considerations that went into Maildir!) And ultimately your
> MTA has to be able to write that format, or there has to be a conversion
> script, which has to be run every 30 seconds, and has to be fast, and
> then we have the same set of problems we have now but in a different
> place.
Your MTA call a MDA like maildrop, and making a specific maildrop in ruby is
pretty easy.
Best regards,
--
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/20080125/cd24b771/attachment.bin
prev parent reply other threads:[~2008-01-25 8:50 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
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 [this message]
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=1201250434-sup-4567@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