Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: Daniel Pittman <daniel@rimspace.net>, <ding@gnus.org>
Subject: Re: Archiving large NNML groups quickly.
Date: Tue, 30 Oct 2001 12:54:05 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.33.0110301245380.27732-100000@slipsten.extundo.com> (raw)
In-Reply-To: <vafbsip1myh.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

On Tue, 30 Oct 2001, Kai Großjohann wrote:

> Simon Josefsson <jas@extundo.com> writes:
> 
> > IMHO the active file should be eliminated, and a ".active" file in
> > each nnml group should be used instead.
> 
> This means that Gnus has to recursively search ~/Mail, at least if
> long file names are not in effect.  This could be quite slow.

No recursive searching is needed, I think, just use the subscribed group
name in Gnus to find the filename.  Of course, instead of reading only 1
file (active) you need to read N files, but it is only necessary to do it
once and after that keep things in memory -- right now the active file is
often read from disk.  So in the end, it would probably be about the same
speed.  When listing all groups, a recursive find is needed though.

Or maybe the active file should simply be removed completely (not replaced
by .active), the active info could be kept in .newsrc.eld (.marks)  
instead.  If we change the format of .marks it would even be simple to
manipulate it from shell/perl scripts.  Hm, what do you think?





  reply	other threads:[~2001-10-30 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  0:05 Daniel Pittman
2001-10-30  1:49 ` Harry Putnam
2001-10-30  9:23 ` Simon Josefsson
2001-10-30  9:44   ` Kai Großjohann
2001-10-30 11:54     ` Simon Josefsson [this message]
2001-10-30 12:50       ` Kai Großjohann
2001-10-30 13:17         ` Per Abrahamsen
2001-10-30 15:58       ` Matt Armstrong
2001-11-01 15:30         ` Steinar Bang
2001-10-30 22:37   ` Harry Putnam

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=Pine.LNX.4.33.0110301245380.27732-100000@slipsten.extundo.com \
    --to=jas@extundo.com \
    --cc=daniel@rimspace.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).