From: patroclo7@gmail.com (Giorgio Lando)
Subject: [sup-talk] header cache
Date: Wed, 16 Jan 2008 23:04:26 +0100 [thread overview]
Message-ID: <1200519319-sup-915@clarabella.clarabella> (raw)
In-Reply-To: <1200516410-sup-1963@south>
> If you look at the log messages, there's one at the emitted at the
> beginning of loading the headers, and one at the end, so you can see
> exactly how much time adding a cache will save you (minus however long
> it takes to load things in from disk).
>
> I'm curious what this number is for 40000 headers. It seems to be about
> 10 seconds for my 5000-message IMAP folder, so I can imagine it being
> quite significant.
I guess you are referring to mutt: in this case I can confirm that the
cache (mutt is compiled with gdbm) saves about 80 secs.
What I meant is that it is nonetheless very slow, and that this is why
one SHOULD NOT ordinarily access an IMAP folder with 40000 headers. In fact I
do not do this in mutt, where on the contrary I enter INBOX and change folder only when
needed (so only seldom I change to All Mail). I can not do exactly the same
with sup: either I pull mails only from the INBOX, but then everything already
archived in gmail through the web interface will
not be seen by sup, or I go with All Mail, but then I have to load each
time 40000 headers, which is extra slow (and would be very slow also with an header cache).
Finally, there would not be any point to pull mails from all the other folders/labels,
because they would include only duplicates of mails in All Mail and they
would not enrich sup index at all.
I have also the feeling that sup's philosophy is not very consistent
with IMAP's philosophy, which is to access the same structure of folders
from different interfaces, syncing immediately any operation on the server,
so that folders and labels are exactly the same from any interface.
Sup follows its own philosophy: thus, it does not deal with folders at all,
and (as you admit often) does not aim to play well with other ways to check emails.
Gmail's imap is not an exception to this conflict between sup's
philosophy and imap's philosophy, because gmail's labels are, when you
access gmail through IMAP, nothing else than folders!
So I have finally decided to go back to POP3, download all mails (including
mails sent from the web interface, in the case of gmail) locally and let sup
index and open them locally. The mails are anyway kept on the server, so
I can also access them through a traditional IMAP client with folders
(such as mutt) or through the web interface when I am around the world
without my laptop.
In this way, I can use sup in a fast way without any bad interplay with
other ways of checking emails. This is very important for me because I
travel a lot and it
is not possible for me to access emails exclusively from my own
computers with sup installed :) .
Thus I do not think that I will go back to access gmail through IMAP
with sup. Anyway I hope to be able to do some testing of the IMAP headers cache
with other small IMAP servers I have access to.
Giorgio
next prev parent reply other threads:[~2008-01-16 22:04 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 [this message]
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
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=1200519319-sup-915@clarabella.clarabella \
--to=patroclo7@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