From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Using DTrace to profile sup-sync
Date: Tue, 18 Dec 2007 20:38:33 -0800 [thread overview]
Message-ID: <1198038994-sup-3413@south> (raw)
In-Reply-To: <1197751337-sup-8140@south>
Excerpts from William Morgan's message of Sat Dec 15 13:04:10 -0800 2007:
> Actually, large IMAP folders will always present a significant problem
> for Sup, because IMAP sucks balls. Short story: Sup has to *always*
> download the headers of the entire mailbox in order to function
> correctly. So every time you start up Sup you're going to be sitting
> there, waiting for that to happen, before you can do anything with
> your IMAP messages.
It might be possible for this not to be the case for well-behaved IMAP
clients, i.e. those that don't change UIDVALIDITY often. If I store the
UIDs directly, then no header pull would be necessary, but a change in
UIDVALIDITY would require a full rescan a la sup-sync --changed.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-12-19 4:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 15:05 Jjgod Jiang
2007-12-15 19:25 ` William Morgan
2007-12-15 19:38 ` William Morgan
2007-12-15 21:04 ` William Morgan
2007-12-19 4:38 ` William Morgan [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=1198038994-sup-3413@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