From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: slow nnimap moves due do many SELECTs
Date: Thu, 30 Sep 2010 10:50:01 -0500 [thread overview]
Message-ID: <87y6aj6xjq.fsf@lifelogs.com> (raw)
In-Reply-To: <m3mxr0i5oy.fsf@quimbies.gnus.org>
On Wed, 29 Sep 2010 23:46:21 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Have you had a chance to try turning off the mark copy on IMAP
>> copy/move? It's making article moves and copies REALLY slow with large
>> IMAP groups and it seems like a simple (negative lines of code) fix.
LMI> I've looked over the code, and Gnus needs to get the article ID back
LMI> from `nnimap-request-move-article' not only for marks copying (which, as
LMI> you point out, can be done on the IMAP level), but also for updating
LMI> active info and stuff. I'm not 100% sure that all that useful,
LMI> though...
LMI> The scenario is that if we copy a message from group A to group B, then
LMI> Gnus (at present) knows immediately that group B has gotten the new
LMI> article, and adjusts the active ranges and the group buffer
LMI> automatically. I think. Let's test... Yes. So that wouldn't work any
LMI> more with the IMAP COPY thing.
LMI> So if we want that to work, we have to SELECT the group we're moving to,
LMI> unfortunately.
OK, I can live with the slowness if it happens once. But currently it
SELECTs the destination group for *every* article move instead of
batching the moves.
Ted
next prev parent reply other threads:[~2010-09-30 15:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 14:19 Ted Zlatanov
2010-09-22 16:53 ` Lars Magne Ingebrigtsen
2010-09-22 17:09 ` Michael Welsh Duggan
2010-09-22 17:17 ` Lars Magne Ingebrigtsen
2010-09-22 17:52 ` Michael Welsh Duggan
2010-09-22 17:57 ` Lars Magne Ingebrigtsen
2010-09-28 13:30 ` Ted Zlatanov
2010-09-29 21:46 ` Lars Magne Ingebrigtsen
2010-09-30 15:50 ` Ted Zlatanov [this message]
2010-09-30 16:35 ` Lars Magne Ingebrigtsen
2010-09-30 16:43 ` Lars Magne Ingebrigtsen
2010-09-30 18:11 ` Ted Zlatanov
2010-09-30 18:16 ` Lars Magne Ingebrigtsen
2010-09-30 16:54 ` Ted Zlatanov
2010-09-30 17:02 ` Lars Magne Ingebrigtsen
2010-09-30 15:22 ` Austin F. Frank
2010-09-22 17:25 ` Ted Zlatanov
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=87y6aj6xjq.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).