From: Russ Allbery <rra@stanford.edu>
Subject: Re: IMAP Performance
Date: 15 Apr 2001 13:44:36 -0700 [thread overview]
Message-ID: <ylvgo5ki4r.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Johan Parin's message of "15 Apr 2001 20:22:00 +0200"
Johan Parin <Johan.Parin@abc.se> writes:
> I don't know what I'm doing wrong (I certainly hope I'm doing something
> wrong), but I have severe performance problem with moving messages to
> IMAP folders.
> Experiment : 100 1-line messages created.
> Gnus
> Move between IMAP folders : 18 1/2 min
> Copy between IMAP folders : 12 min
> Netscape/Win
> Copy between IMAP folders : about 2 seconds
> (the folders are on the same IMAP server)
Moving and copying messages is rather slow in nnml too. I'd love to see
that fixed. It really shouldn't take hours, or even minutes, to move a
few thousand messages between nnml groups if one can use rename() in the
underlying file system (and Gnus can always fall back to a copy if it
can't).
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2001-04-15 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 18:22 Johan Parin
2001-04-15 18:44 ` simon
2001-04-15 20:44 ` Russ Allbery [this message]
2001-04-16 11:59 ` Karl Kleinpaste
2001-04-16 20:40 ` Paul Jarc
2001-04-16 22:43 ` Russ Allbery
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=ylvgo5ki4r.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).