From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/82123 Path: news.gmane.org!not-for-mail From: Steinar Bang Newsgroups: gmane.emacs.gnus.general Subject: Re: What happened to snappy low-bandwidth nnimap? Date: Wed, 08 Aug 2012 20:46:38 +0200 Organization: Probably a good idea Message-ID: <87fw7xrzld.fsf@dod.no> References: <87sjby8rpx.fsf@randomsample.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1344451698 6412 80.91.229.3 (8 Aug 2012 18:48:18 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 8 Aug 2012 18:48:18 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M30391@lists.math.uh.edu Wed Aug 08 20:48:19 2012 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SzBIl-0004dU-I1 for ding-account@gmane.org; Wed, 08 Aug 2012 20:48:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1SzBHn-0001EW-JR; Wed, 08 Aug 2012 13:47:15 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1SzBHm-0001EM-0l for ding@lists.math.uh.edu; Wed, 08 Aug 2012 13:47:14 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1SzBHX-0002R8-Lf for ding@lists.math.uh.edu; Wed, 08 Aug 2012 13:47:13 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1SzBHV-0001Bt-Km for ding@gnus.org; Wed, 08 Aug 2012 20:46:57 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SzBHQ-0002XD-8U for ding@gnus.org; Wed, 08 Aug 2012 20:46:52 +0200 Original-Received: from cm-84.208.231.161.getinternet.no ([84.208.231.161]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 08 Aug 2012 20:46:52 +0200 Original-Received: from sb by cm-84.208.231.161.getinternet.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 08 Aug 2012 20:46:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 39 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cm-84.208.231.161.getinternet.no Mail-Copies-To: never User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:gRu4x636NoxPdzEiQov4eIhWjPY= X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:82123 Archived-At: >>>>> Richard Riley : > David Engster writes: [snip!] >> 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". [snip!] > 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...? I haven't noticed it myself, but that probably means I don't have slow enough lines even when on mobile networks. So I can't do the bisect myself. What I do when bisecting, is: 1. git bisect start HEAD good-commit (for "good commit" pick one that you're sure is back when things were OK) 2. compile, with eg. (cd ~/git/gnus; make clean; make; cd lisp; make tags) 3. start a new emacs, start gnus, and test 4. If the nnimap operations were slow, do: git bisect bad If the nnimap operations were fast, do: git bisect good If git reports it has found the offending commit, move to step 5, otherwise move to step 2. and repeat from there 5. Report the offending commit, then clean up the working directory: git bisect reset git checkout master