From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>,
"David Maus" <dmaus@ictsoc.de>
Subject: (gnus-summary-goto-article <message-id>) extremely slow for certain IMAP server
Date: Mon, 26 Jul 2010 20:42:04 +0200 [thread overview]
Message-ID: <201007262042.04971.tassilo@member.fsf.org> (raw)
Hi all,
I maintain Org-mode's org-gnus.el, which allows linking to Gnus articles
in Org-mode. Links to articles are stored by their group and their
message-id. When following a link a call like
(gnus-summary-goto-article <message-id>)
will be done. Unfortunately, for Sébastien (in Cc) this call to a
message on some IMAP server takes ages for bigger groups (~5 minutes).
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, 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.
Or can this call to `imap-search' somehow be omitted by optional Gnus
features like the gnus registry?
You can check the full Org-mode thread with the report and all debugging
details at
http://thread.gmane.org/gmane.emacs.orgmode/26722/focus=27590
Bye,
Tassilo
next reply other threads:[~2010-07-26 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 18:42 Tassilo Horn [this message]
2010-07-26 19:27 ` David Engster
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=201007262042.04971.tassilo@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.org \
--cc=dmaus@ictsoc.de \
--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).