From: Dave Love <fx@gnu.org>
To: Bjorn Solberg <bjorn_ding2@hekneby.org>
Cc: Simon Josefsson <simon@josefsson.org>,
"ding@gnus.org" <ding@gnus.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: IMAP and Exchange 2007 - imap-fetch-safe
Date: Sat, 17 Jan 2009 20:59:09 +0000 [thread overview]
Message-ID: <87zlhpbqea.fsf@liv.ac.uk> (raw)
In-Reply-To: <m3eiz7kql3.fsf@famsolberg.com> (Bjorn Solberg's message of "Tue, 13 Jan 2009 18:28:56 +0000")
Bjorn Solberg <bjorn_ding2@hekneby.org> writes:
> and everything still works fine, albeit slow. Fetching new mail and
> using nnimap-split-inbox '("INBOX") and nnimap-split-rule processes
> about 2s/header or 1/2 header/sec.
It's not obviously slow for me (on a fast machine, these days), but I
haven't tried to time it against, say, Evolution. I think there is too
much consing going on, but not necessarily in the IMAP code. M-x
elp-instrument-package should reveal any bottleneck.
prev parent reply other threads:[~2009-01-17 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87iqphil5p.fsf@liv.ac.uk>
[not found] ` <87ocz3n8d4.fsf@marauder.physik.uni-ulm.de>
[not found] ` <87iqpa99wy.fsf@liv.ac.uk>
[not found] ` <87wsde7t5j.fsf_-_@marauder.physik.uni-ulm.de>
[not found] ` <86mye95p27.fsf@lifelogs.com>
[not found] ` <878wpt48qj.fsf@marauder.physik.uni-ulm.de>
[not found] ` <86d4eyvryx.fsf@lifelogs.com>
[not found] ` <878wplcxws.fsf@marauder.physik.uni-ulm.de>
[not found] ` <87k58za3q8.fsf@liv.ac.uk>
2009-01-13 17:00 ` IMAP and Exchange 2007 - imap-fetch-safe (was: FIXMEs in imap.el and nnimap.el) Reiner Steib
2009-01-13 17:20 ` IMAP and Exchange 2007 - imap-fetch-safe Simon Josefsson
2009-01-17 20:58 ` Dave Love
2009-01-31 15:27 ` Reiner Steib
2009-02-01 15:43 ` Bjorn Solberg
2009-02-02 19:15 ` Reiner Steib
2009-01-13 18:28 ` Bjorn Solberg
2009-01-17 20:59 ` Dave Love [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zlhpbqea.fsf@liv.ac.uk \
--to=fx@gnu.org \
--cc=bjorn_ding2@hekneby.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=simon@josefsson.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).