From: David Engster <deng@randomsample.de>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: ding@gnus.org, "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>,
"David Maus" <dmaus@ictsoc.de>
Subject: Re: (gnus-summary-goto-article <message-id>) extremely slow for certain IMAP server
Date: Mon, 26 Jul 2010 21:27:13 +0200 [thread overview]
Message-ID: <87pqyayrfy.fsf@randomsample.de> (raw)
In-Reply-To: <201007262042.04971.tassilo@member.fsf.org> (Tassilo Horn's message of "Mon, 26 Jul 2010 20:42:04 +0200")
Tassilo Horn writes:
> We've edebugged and profiled the gnus code, and the culprit is the
> function `nnimap-request-article-part'. When given a message-id instead
> of an article number, that function will query the IMAP server with
> `imap-search', and then emacs hangs 5 minutes till the server finally
> responds.
>
> Ok, it's basically the server's fault,
Yes. An IMAP server should be able to retrieve articles based on
message-id's very quickly, since this is a pretty common task.
> but can't Gnus do any better? Especially, the mapping message-id to
> article number is also contained in the .overview file of the group,
> but it seems that this file is not checked.
Yes. You could use nnimap-retrieve-headers-from-file and check if you
find the MID there.
> Or can this call to `imap-search' somehow be omitted by optional Gnus
> features like the gnus registry?
Probably, but currently the registry does not keep track of the article
numbers, only of the groups. I guess this could easily be added, though?
But why don't you just save the article number together with the
message-id in the link?
-David
next prev parent reply other threads:[~2010-07-26 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 18:42 Tassilo Horn
2010-07-26 19:27 ` David Engster [this message]
2010-07-26 19:43 ` Tassilo Horn
2010-07-26 20:29 ` David Engster
2010-07-26 21:08 ` Ted Zlatanov
2010-07-26 21:29 ` David Engster
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=87pqyayrfy.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
--cc=dmaus@ictsoc.de \
--cc=tassilo@member.fsf.org \
--cc=wxhgmqzgwmuf@spammotel.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;
as well as URLs for NNTP newsgroup(s).