From: Steinar Bang <sb@metis.no>
Subject: nnimap bottlenecks? (Was: nnimap: article moving)
Date: 02 Jan 2001 20:54:40 +0100 [thread overview]
Message-ID: <whae9991bz.fsf_-_@viffer.computas.no> (raw)
In-Reply-To: <ilug0j2qn1a.fsf@barbar.josefsson.org>
>>>>> Simon Josefsson <sj@extundo.com>:
> NAGY Andras <nagya@inf.elte.hu> writes:
>> Been curious how efficiently nnimap works
> Nnimap is painfully slow.
> At some point (or rather an interval) in time, I hope to extend the
> Gnus<->backend interface to make IMAP groups work much faster.
> Don't blame IMAP for nnimap speed, IMAP can be very fast.
I'm curious: what are the current bottleneck(s) of nnimap?
>From messages in the minibuffer, it seems that on a `g' it waits for
the completion of the check for new articles in each group, before
skipping to the next. Is this one of the bottlenecks?
next prev parent reply other threads:[~2001-01-02 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 23:19 nnimap: article moving NAGY Andras
2001-01-01 23:24 ` NAGY Andras
2001-01-02 10:13 ` Simon Josefsson
2001-01-02 19:54 ` Steinar Bang [this message]
2001-01-02 21:09 ` nnimap bottlenecks? (Was: nnimap: article moving) Simon Josefsson
2001-01-03 8:02 ` Soeren Laursen
2001-01-04 8:39 ` Simon Josefsson
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=whae9991bz.fsf_-_@viffer.computas.no \
--to=sb@metis.no \
/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).