From: Michael Welsh Duggan <mwd@cert.org>
To: ding@gnus.org
Subject: Re: What happened to snappy low-bandwidth nnimap?
Date: Wed, 08 Aug 2012 16:21:38 -0400 [thread overview]
Message-ID: <tntehnhf831.fsf@waterbuck.yellow.cert.org> (raw)
In-Reply-To: <87boil888i.fsf@randomsample.de> (David Engster's message of "Wed, 08 Aug 2012 22:00:13 +0200")
David Engster <deng@randomsample.de> writes:
> Steinar Bang writes:
>>>>>>> Richard Riley <rileyrg@gmail.com>:
>>> David Engster <deng@randomsample.de> writes:
>>
>>>> Gnus' nnimap used to be pretty snappy with low bandwidths, but now I
>>>> get "Initial sync of 2 groups (please wait)" and it downloads about
>>>> 700kb of data. While that in itself is pretty bad, I could probably
>>>> live with it if it actually did this once, but it does it almost
>>>> *every* time; so much for "initial".
>>
>>> Having spent a lot of time getting to understand agent, queues, plugging
>>> and levels and level specific downloads last summer on holiday I too
>>> have now noted that imap connections are really really slow on low
>>> bandwidth connections and it appears to be fetching a lot of data
>>> despite nothing being new.
>>
>> I guess it would be neat if one of you could use git bisect to find the
>> commit that triggered the behaviour...?
>
> It's not that easy since actual messaging of these "initial sync"
> thingies was added later. After looking into the logs it seems it has to
> do with QRESYNC handling; I'm using Dovecot 1.2 and it should support
> QRESYNC, hence I don't understand why I'm seeing so many "initial
> syncs". It could be because my connection drops frequently (as I've
> said, reception is terrible).
In <kslijqdw90.fsf@netfonds.no>
(<URL:http://article.gmane.org/gmane.emacs.gnus.general/81943>), Peder
Klingenberg gives a diagnosis of this problem.
--
Michael Welsh Duggan
(mwd@cert.org)
next prev parent reply other threads:[~2012-08-08 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 18:47 David Engster
2012-08-08 15:41 ` Richard Riley
2012-08-08 18:46 ` Steinar Bang
2012-08-08 20:00 ` David Engster
2012-08-08 20:21 ` Michael Welsh Duggan [this message]
2012-08-08 20:36 ` David Engster
2012-08-09 20:26 ` David Engster
2012-09-04 22:09 ` Lars Ingebrigtsen
2012-08-08 20:03 ` Dave Abrahams
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=tntehnhf831.fsf@waterbuck.yellow.cert.org \
--to=mwd@cert.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).