From: Vegard Vesterheim <vegard.vesterheim@uninett.no>
To: ding@gnus.org
Subject: Gcc to IMAP is slow
Date: Mon, 25 Oct 2010 10:03:33 +0200 [thread overview]
Message-ID: <1sr5fek8bu.fsf@voll.uninett.no> (raw)
In order to preserve threads as much as possible, I Gcc my own messages
both into the folder I am in, and to the Sent-folder (via
gnus-outgoing-message-group)). But this is now much slower than before
the IMAP rewrite. My emacs can get unresponsive for many seconds after I
have sent a message. The imap log shows that gnus is doing a IMAP SEARCH
for a Message-Id, which I guess can be slow on large folders:
09:45:15 920 SELECT "INBOX"
09:45:15 921 UID FETCH 1:* FLAGS
09:45:16 922 APPEND "INBOX" {786}
09:45:16 923 UID SEARCH HEADER Message-Id "<1ssjzuk96c.fsf@voll.uninett.no>"
09:45:22 924 SELECT "Sent"
09:45:22 925 SELECT "Sent"
09:45:22 926 UID FETCH 1:* FLAGS
09:45:22 927 APPEND "Sent" {786}
09:45:22 928 UID SEARCH HEADER Message-Id "<1ssjzuk96c.fsf@voll.uninett.no>"
Any hints on how to fix this?
- Vegard V -
next reply other threads:[~2010-10-25 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 8:03 Vegard Vesterheim [this message]
2010-10-25 17:16 ` Steinar Bang
2010-10-25 21:42 ` Vegard Vesterheim
2010-10-29 22:47 ` Lars Magne Ingebrigtsen
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=1sr5fek8bu.fsf@voll.uninett.no \
--to=vegard.vesterheim@uninett.no \
--cc=ding@gnus.org \
/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).