From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Re: Performance problem of imap move
Date: Tue, 27 Jan 2015 21:06:06 -0500 [thread overview]
Message-ID: <84twzb64mp.fsf@davestoy.home> (raw)
In-Reply-To: <upzc7fw8xp3e.fsf@dod.no> (Steinar Bang's message of "Tue, 27 Jan 2015 15:41:57 +0100")
It appears that the change associated with this thread has caused a problem for me at work. After doing a git pull and recompiling (as usual) I noticed some strangeness with some of the groups on our office365 set up. I use a group line format of
%S%p%P%(%G [(%y new,%T !,%I ?)/~%t]%)
A number of groups, though not all, initially showed up with all the article counts showing as a '*'. Running M-g on the group resulted in an error that I regret not recording. I then ran M-c to clear data and M-g again and the article counts showed as ridiculously high and Emacs hung long enough when trying to enter the group that Gnome offered to kill it off for lack of response. I ran git bisect and it determined that this
447c56af7cb2afac14a0f3ed23f85d907c443a5d is the first bad commit
commit 447c56af7cb2afac14a0f3ed23f85d907c443a5d
Author: Lars Ingebrigtsen <larsi@gnus.org>
Date: Mon Jan 26 13:50:20 2015 +1100
Make moving IMAP articles faster in large groups
* lisp/gnus-group.el (gnus-group-get-new-news-this-group): Explicitly
request rescans when being run interactively.
* lisp/gnus-int.el (gnus-request-group-scan): New backend function.
* lisp/nnimap.el (nnimap-request-scan-group): Implement in on IMAP.
* lisp/nnimap.el (nnimap-request-group): Don't rescan the group here,
because that can be very slow in large groups.
:040000 040000 3164108231527becdb471bfe74ce22bdd3bc5b4f
d424a0d925e35e71fc30863580e2ca949559505e M lisp
While many of the affected groups don't really matter much to me (they mostly represent archives) a couple of them regularly receive messages either as a result of server side splitting or article moves so I'm currently running a detached checkout on the last working commit. I am happy to take some time to try to help debug this but I need some guidance on what to do and what to look for. I've stepped through the lisp debugger in the past but I wouldn't even know where to begin in this case. In particular if I need to look at what's going on IMAP-wise I don't know how to do that.
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2015-01-28 2:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 19:06 Mickaël Rémond
2015-01-21 14:11 ` Mickaël Rémond
2015-01-25 4:57 ` Lars Ingebrigtsen
2015-01-26 2:52 ` Lars Ingebrigtsen
2015-01-26 12:11 ` Tassilo Horn
2015-01-26 16:55 ` Steinar Bang
2015-01-27 0:54 ` Lars Ingebrigtsen
2015-01-27 7:23 ` Tassilo Horn
2015-01-27 7:28 ` Tassilo Horn
2015-01-27 7:30 ` Lars Ingebrigtsen
2015-01-27 8:01 ` Tassilo Horn
2015-01-27 8:05 ` Tassilo Horn
2015-01-28 0:45 ` Lars Ingebrigtsen
2015-01-27 3:46 ` Eric Abrahamsen
2015-01-27 4:48 ` Lars Ingebrigtsen
2015-01-27 5:02 ` Eric Abrahamsen
2015-01-27 5:09 ` Lars Ingebrigtsen
2015-01-27 14:41 ` Steinar Bang
2015-01-28 2:06 ` Dave Goldberg [this message]
2015-01-29 5:11 ` Dave Goldberg
2015-01-28 2:29 ` Eric Abrahamsen
2015-01-28 4:08 ` Eric Abrahamsen
2015-01-28 4:10 ` Eric Abrahamsen
2015-01-28 4:32 ` Eric Abrahamsen
2015-01-28 5:08 ` Lars Ingebrigtsen
2015-01-28 5:13 ` Lars Ingebrigtsen
2015-01-28 5:52 ` Eric Abrahamsen
2015-01-28 14:22 ` Tassilo Horn
2015-01-29 1:08 ` 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=84twzb64mp.fsf@davestoy.home \
--to=david.goldberg6@verizon.net \
--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).