[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Gnus horribly slow after upgrade to Fedora17

From: Otto J. Makela
Subject: Re: Gnus horribly slow after upgrade to Fedora17
Date: Sat, 03 Aug 2013 12:17:17 +0300
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Lars Magne Ingebrigtsen <> wrote:

> (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 LIST ACTIVE zzz.3
20130803T103514.532 LIST ACTIVE zz.unity.netlink
20130803T103514.542 LIST ACTIVE
20130803T103514.552 LIST ACTIVE zybrkat.mlemke
20130803T103514.561 LIST ACTIVE zippo.spamhippo.top100
20130803T103514.571 LIST ACTIVE zippo.editorial
20130803T103514.581 LIST ACTIVE
20130803T103514.591 LIST ACTIVE zetnet.local
20130803T103514.600 LIST ACTIVE zeta.test.ausadmin
20130803T103514.611 LIST ACTIVE 
20130803T103938.977 LIST ACTIVE 0.verizon.windowsxp
20130803T103938.985 LIST ACTIVE
20130803T103938.995 LIST ACTIVE 0.verizon.newsgroup.requests
20130803T103939.004 LIST ACTIVE 0.verizon.linux
20130803T103939.015 LIST ACTIVE 0.verizon.flame
20130803T103939.024 LIST ACTIVE 0.verizon.discussion-general
20130803T103939.034 LIST ACTIVE 0.verizon.announce
20130803T103939.043 LIST ACTIVE 0.verizon.adsl
20130803T103939.055 LIST ACTIVE 0.test
20130803T103939.063 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 ""
        (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 
(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
      (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 * * * * * * */

reply via email to

[Prev in Thread] Current Thread [Next in Thread]