From: mremond@process-one.net
To: info-gnus-english@gnu.org
Subject: Performance problem of IMAP move (Gmail)
Date: Tue, 6 Jan 2015 12:27:03 -0800 (PST) [thread overview]
Message-ID: <b64e5c67-1659-4d47-b7bd-216a0f6ddb54@googlegroups.com> (raw)
Hello,
I am currently trying to trouble shoot performance problem of the nnimap
move methods. It takes more than 30 seconds here to move a mail (I am
using Gmail) on imap on the same server.
imap server is a secondary server.
Here is the result of elp instrument:
gnus-summary-move-article 2 72.684064 36.342032
gnus-activate-group 2 62.887769 31.4438845
gnus-group-get-new-news-this-group 1 62.887473 62.887473
gnus-group-completing-read 2 8.951666 4.475833
gnus-completing-read 2 8.9514789999 4.4757394999
gnus-emacs-completing-read 2 8.951453 4.4757265
gnus-read-move-group-name 2 4.755247 2.3776235
gnus-y-or-n-p 1 4.516911 4.516911
gnus-request-set-mark 2 3.040978 1.520489
gnus-request-move-article 1 1.9702929999 1.9702929999
Any idea what I should do to pinpoint the issue ?
Thanks !
--
Mickaël Rémond
next reply other threads:[~2015-01-06 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 20:27 mremond [this message]
2015-01-07 7:17 ` Denis Bitouzé
2015-01-29 3:18 ` Lars 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=b64e5c67-1659-4d47-b7bd-216a0f6ddb54@googlegroups.com \
--to=mremond@process-one.net \
--cc=info-gnus-english@gnu.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).