From: simon@josefsson.org
Cc: ding@gnus.org
Subject: Re: IMAP Performance
Date: 15 Apr 2001 20:44:22 +0200 [thread overview]
Message-ID: <hezqxat5.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <m3u23qgh13.fsf@johanspc.abc.se>
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)
You can evaluate `(setq imap-log "*imap-log*")' to log what is being
sent to and received from the server, and then observe at least a few
mailbox (re-)selects per moved message, making things slow. The next
step would be to optimize nnimap for batch moving/copying and sending
patches. :)
Without modifying code, perhaps you could use splitting to move
messages were you want them? (And then leave them there.) I know it
doesn't solve the real problem.
next prev parent reply other threads:[~2001-04-15 18: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 [this message]
2001-04-15 20:44 ` Russ Allbery
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=hezqxat5.fsf@barbar.josefsson.org \
--to=simon@josefsson.org \
--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).