Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Gnus' speed
Date: Wed, 29 Jul 2009 13:59:56 +0200	[thread overview]
Message-ID: <m2d47j1yyr.fsf@gwdg-mac-engster.top.gwdg.de> (raw)
In-Reply-To: <vxkfxcfvjiv.fsf@awol.kleinpaste.org> (Karl Kleinpaste's message of "Wed, 29 Jul 2009 07:03:04 -0400")

Karl Kleinpaste <karl@kleinpaste.org> writes:
> David Engster <deng@randomsample.de> writes:
>> * Scoring in general is slow. For maximum speed, one should omit
>>   scoring completely.
>
> I am surprised that anyone would want to do away with scoring; its
> utility is so high in terms of determining what is/isn't worth reading
> that, even if slow, it is too valuable to ignore.
>
> That said, I don't find it slow.  I even have an "all" scorefile along
> with the usual per-group scorefiles, and I don't perceive any special
> penalty from using scoring.

It depends on the scoring you do. If you score against the whole head or
even the body, scoring becomes incredibly slow since Gnus has to request
the head/body, resp.

For example, I have a group with a score file like

(("head"
  ("somestring" nil nil s)))

and reading its ~940 articles takes ages:

gnus-score-headers                                                            1           40.348502     40.348502
gnus-score-body                                                               1           40.346746     40.346746
gnus-request-head                                                             938         40.214296000  0.0428723837

Scoring just against the basic headers like from/to/subject probably
does not have this problem.

-David



  reply	other threads:[~2009-07-29 11:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 18:34 Daniel Clemente
2009-07-28 21:03 ` Leo
2009-07-29  8:03   ` Daniel Clemente
2009-07-29  8:44     ` David Engster
2009-07-29 11:03       ` Karl Kleinpaste
2009-07-29 11:59         ` David Engster [this message]
2009-07-29 12:26           ` Karl Kleinpaste
2009-07-29 12:44             ` David Engster
2009-07-29 18:30               ` Ted Zlatanov
2009-07-29 20:19                 ` Tom Tromey
2009-07-30  6:03                   ` Daniel Pittman
2009-07-31  6:30                 ` Bill White
2009-07-29 18:46           ` Reiner Steib
2009-08-15  1:07           ` Miles Bader
2009-08-15  1:50             ` Daniel Pittman
2009-07-29 18:25       ` Ted Zlatanov
2009-07-29  9:47     ` Leo
2009-07-29 18:24     ` Ted Zlatanov
2009-07-30  5:58       ` Daniel Pittman
2009-07-30 13:33         ` Ted Zlatanov
2009-07-31  5:06           ` Daniel Pittman
2009-08-02 14:20       ` Steinar Bang
2009-08-03 14:38         ` Ted Zlatanov
2009-07-30  5:59     ` Daniel Pittman
2009-07-29  7:07 ` CHENG Gao
2009-07-29 18:20   ` nnrss through Google Reader (was: Gnus' speed) Ted Zlatanov
2009-07-31 13:44     ` nnrss through Google Reader Ted Zlatanov
2009-07-30  0:38   ` Gnus' speed Kevin Ryde
2009-07-29 18:55 ` Reiner Steib
2009-07-30  0:29   ` Kevin Ryde
2009-07-30  7:41     ` Adam Sjøgren
2009-08-04  1:10       ` Kevin Ryde
2009-08-15  1:11     ` Miles Bader
2009-08-15  8:28       ` Steinar Bang
2009-08-16  3:50         ` Miles Bader
2009-08-04 17:48   ` Daniel Clemente
2009-08-04 17:46 ` Daniel Clemente
2009-08-05  5:52   ` Steinar Bang
2009-08-05  5:55     ` Steinar Bang
2009-08-05  8:20       ` Daniel Clemente
2009-08-05 15:10         ` Steinar Bang

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=m2d47j1yyr.fsf@gwdg-mac-engster.top.gwdg.de \
    --to=deng@randomsample.de \
    --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).