From: Olaf Klischat <klischat@cs.tu-berlin.de>
Subject: nnimap summary generation slowness
Date: Sun, 23 Oct 2005 08:24:24 +0200 [thread overview]
Message-ID: <m27jc4699j.fsf@cs.tu-berlin.de> (raw)
My "INBOX" IMAP folder on my mail server has 313 messages in it.
In the group buffer I hit "- SPC" (i.e. (gnus-topic-read-group t)) on
the folder.
Ethereal show this chatter on the IMAP connection:
10307 UID SEARCH UNSEEN UNDELETED
* SEARCH 60204 60205 60206
10307 OK Completed
10308 UID SEARCH SEEN
* SEARCH 50683 50830 [...308 numbers...] 60148 60180 60203
10308 OK Completed
10309 UID SEARCH FLAGGED
* SEARCH
10309 OK Completed
10310 UID SEARCH ANSWERED
* SEARCH
10310 OK Completed
10311 UID SEARCH KEYWORD gnus-save
* SEARCH
10311 OK Completed
10312 UID SEARCH KEYWORD gnus-forward
* SEARCH
10312 OK Completed
10313 UID SEARCH RECENT
* SEARCH 60204 60205 60206
10313 OK Completed
It takes less than a second to complete. Then, Gnus asks:
"How many articles from nnimap+server:INBOX (default 9521):"
Obviously, 9521 is the size of the interval 50683...60203 (why didn't
it just count the numbers returned to the "UID SEARCH SEEN" command to
get the *correct* number of messages?).
Anyway, I hit ENTER to see all messages.
Another conversation with the server takes place, again just fractions
of a second long:
10314 UID SEARCH UID 50683:60203
* SEARCH 50683 50830 [...308 numbers...] 60148 60180 60203
10314 OK Completed
After that, Gnus eats lots of CPU time for ~5 minutes without either
updating the UI or sending/receiving a single byte to/from the IMAP
server. Then, the summary buffer appears, with the 313 messages in it.
Obviously, there's a lot of air somewhere in there waiting to be
squeezed out.
Olaf
reply other threads:[~2005-10-23 6:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m27jc4699j.fsf@cs.tu-berlin.de \
--to=klischat@cs.tu-berlin.de \
/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;
as well as URLs for NNTP newsgroup(s).