From: Lars Ingebrigtsen <larsi@gnus.org>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: ding@gnus.org
Subject: Re: move article painfully slow over imap
Date: Wed, 28 Jan 2015 14:48:30 +1100 [thread overview]
Message-ID: <87fvavzhtd.fsf@building.gnus.org> (raw)
In-Reply-To: <87silhgmif.fsf@gmail.com> (Carlos Pita's message of "Thu, 31 Jul 2014 20:02:32 -0300")
Carlos Pita <carlosjosepita@gmail.com> writes:
> I'm using gnus-summary-move-article to move messages to gmail trash over
> an imap connection. Moving a single message takes several
> seconds. Moving a list of messages has more or less O(n) with the same
> constant. So it's slow for one article and it's proportionally slow for
> n articles (no decreasing average cost here, batching the moves is not
> optimizing on some fixed initial cost or whatever).
This should be fixed in the current git Gnus, but there's apparently new
problems associated in this area that haven't been worked out yet. But
will hopefully be within a couple of days. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2015-01-28 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 23:02 Carlos Pita
2015-01-28 3:48 ` Lars Ingebrigtsen [this message]
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=87fvavzhtd.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=carlosjosepita@gmail.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).