Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@metis.no>
Subject: opening speed for nnml groups
Date: 02 Sep 1997 14:01:31 +0200	[thread overview]
Message-ID: <whbu2bq604.fsf@norne.troll.no> (raw)

I haven't done any timing of it yet, but it seems like opening nnml
groups get noticably slower, as the groups get bigger (with more
ticked or read articles in them).

I was sort of idly wondering where the speed hit was?  Is it in the
parsing of the .overview file?

I remember that slow exit on big or sparse nnml group, was a problem
when you did expiry on exiting a group, so I went for demonical
expiry, as well as demonical fetch and sort.

If the reading and parsing of the .overview file is the problem, would
it be an idea to cache the parsed info between visits? And update it
during fetch and sort operations?

Or is that too expensive memory-wise?


             reply	other threads:[~1997-09-02 12:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-02 12:01 Steinar Bang [this message]
1997-09-03 13:05 ` Steve Folkes
1997-09-03 15:01   ` Lars Balker Rasmussen
1997-09-03 19:45     ` Mark Eichin
1997-09-03 21:26     ` Russ Allbery
1997-09-04 14:55     ` Sean Doran
1997-09-04 15:39       ` Lars Balker Rasmussen
1997-09-04 21:44         ` Colin Rafferty
1997-09-05 12:20           ` David S. Goldberg
1997-09-05 15:21             ` Edit MIME messages (was: Re: opening speed for nnml groups) Kai Grossjohann
1997-09-05 15:57               ` David S. Goldberg
1997-09-09  7:06                 ` Steinar Bang
1997-09-10  8:43             ` opening speed for nnml groups Lars Balker Rasmussen
1997-09-10 15:07               ` Colin Rafferty
1997-09-13 23:54               ` Lars Magne Ingebrigtsen
1997-09-03 20:33 ` Ken Raeburn

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=whbu2bq604.fsf@norne.troll.no \
    --to=sb@metis.no \
    /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).