From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/16470 Path: news.gmane.org!not-for-mail From: om@iki.fi (Otto J. Makela) Newsgroups: gmane.emacs.gnus.user Subject: Re: Gnus horribly slow after upgrade to Fedora17 Date: Sat, 03 Aug 2013 12:17:17 +0300 Organization: Games and Theory Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1375521605 26941 80.91.229.3 (3 Aug 2013 09:20:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 3 Aug 2013 09:20:05 +0000 (UTC) To: info-gnus-english@gnu.org Original-X-From: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Sat Aug 03 11:20:08 2013 Return-path: Envelope-to: gegu-info-gnus-english@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1V5Y0N-0002hx-8F for gegu-info-gnus-english@m.gmane.org; Sat, 03 Aug 2013 11:20:07 +0200 Original-Received: from localhost ([::1]:44069 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V5Y0M-0007ME-4A for gegu-info-gnus-english@m.gmane.org; Sat, 03 Aug 2013 05:20:06 -0400 Original-Path: usenet.stanford.edu!goblin1!goblin2!goblin.stu.neva.ru!newsfeed1.swip.net!newsfeed2.funet.fi!newsfeeds.funet.fi!feeder1.news.elisa.fi!uutiset.elisa.fi!7564ea0f!not-for-mail Original-Newsgroups: gnu.emacs.gnus X-Face: 'g'S,X"!c; \pfvl4ljdcm?cDdk<-Z; `x5; YJPI-cs~D%; _<\V3!3GCims?a*; ~u$ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Original-Sender: info-gnus-english-bounces+gegu-info-gnus-english=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.gnus.user:16470 Archived-At: Lars Magne Ingebrigtsen wrote: > om@iki.fi (Otto J. Makela) writes: >> gnus-read-active-file's value is some >> gnus-check-new-newsgroups's value is ask-server > > That should be OK, then. Hm... > > Could you set `nntp-record-commands', hit `g' and look in the > *nntp-log* buffer and see what it contains? After this, it contained 26881 lines, where gnus does LIST ACTIVE for each and every group in the .newsrc: 20130803T103514.522 news.saunalahti.fi LIST ACTIVE zzz.3 20130803T103514.532 news.saunalahti.fi LIST ACTIVE zz.unity.netlink 20130803T103514.542 news.saunalahti.fi LIST ACTIVE zz.unity.chat 20130803T103514.552 news.saunalahti.fi LIST ACTIVE zybrkat.mlemke 20130803T103514.561 news.saunalahti.fi LIST ACTIVE zippo.spamhippo.top100 20130803T103514.571 news.saunalahti.fi LIST ACTIVE zippo.editorial 20130803T103514.581 news.saunalahti.fi LIST ACTIVE zetnet.support 20130803T103514.591 news.saunalahti.fi LIST ACTIVE zetnet.local 20130803T103514.600 news.saunalahti.fi LIST ACTIVE zeta.test.ausadmin 20130803T103514.611 news.saunalahti.fi LIST ACTIVE zer.z-netz.wissenschaft.psychologie ... 20130803T103938.977 news.saunalahti.fi LIST ACTIVE 0.verizon.windowsxp 20130803T103938.985 news.saunalahti.fi LIST ACTIVE 0.verizon.suggestion.box 20130803T103938.995 news.saunalahti.fi LIST ACTIVE 0.verizon.newsgroup.requests 20130803T103939.004 news.saunalahti.fi LIST ACTIVE 0.verizon.linux 20130803T103939.015 news.saunalahti.fi LIST ACTIVE 0.verizon.flame 20130803T103939.024 news.saunalahti.fi LIST ACTIVE 0.verizon.discussion-general 20130803T103939.034 news.saunalahti.fi LIST ACTIVE 0.verizon.announce 20130803T103939.043 news.saunalahti.fi LIST ACTIVE 0.verizon.adsl 20130803T103939.055 news.saunalahti.fi LIST ACTIVE 0.test 20130803T103939.063 news.saunalahti.fi LIST ACTIVE - So no wonder it is slow, now I need to figure out why this happens. This is what my .gnus has: ---- (setq gnus-select-method '(nntp "news.saunalahti.fi" (nntp-open-connection-function network-only))) (setq gnus-default-posting-charset 'iso-8859-1) (setq message-default-charset 'iso-8859-1) (setq gnus-check-new-newsgroups 'ask-server) (setq gnus-save-killed-list nil) (setq gnus-user-cross-reference t) (setq gnus-thread-indent-level 2) (setq gnus-ignored-headers "^Xref:\\|^X-Trace:\\|^Mime-Version:\\|^X-Newsreader:") (setq gnus-boring-article-headers '(empty followup-to reply-to newsgroups)) (setq gnus-article-date-local t) (setq gnus-treat-date-local 'head) (add-hook 'message-sent-hook 'gnus-score-followup-thread '10) (setq gnus-summary-line-format "%U%R%z%I%[%3L:%-17,17f%d%] %s\n") (setq gnus-article-mode-line-format "%1,40S") (setq gnus-summary-expunge-below -1500) (setq gnus-score-expiry-days 10) (setq gnus-use-nocem t) (setq gnus-nocem-check-article-limit 50) (setq gnus-refer-article-method '(current (nnweb "refer" (nnweb-type google)))) (setq gnus-thread-sort-functions '(gnus-thread-sort-by-number gnus-thread-sort-by-total-score)) ; gnus-thread-hide-subjects nil ; gnus-thread-hide-subtree t ; gnus-thread-indent-level 4) ;; (setq gnus-summary-same-subject "->") (setq gnus-summary-gather-subject-limit 'fuzzy) (setq gnus-simplify-subject-fuzzy-regexp "\\([Vv][Ss]\\|[Ss][Vv]\\):[ \t]*") ---- [...] >> Also, do you have ideas on correcting the nntp connection error >> I detailed in my earlier message? > > I think I missed that message? It was the connection problem which turns out to already be fixed: Anssi Saari wrote: > I reported that issue following the discussion last year and Lars > fixed it in December or thereabouts. He said then the fix will be > included in the Gnus that goes with Emacs 24.4. I guess it was too > late to get it into Emacs 24.3 at that point. -- /* * * Otto J. Makela * * * * * * * * * */ /* Phone: +358 40 765 5772, ICBM: N 60 10' E 24 55' */ /* Mail: Mechelininkatu 26 B 27, FI-00100 Helsinki */ /* * * Computers Rule 01001111 01001011 * * * * * * */