Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: Holes in article sequence
Date: 09 Jul 1999 19:11:09 +0200	[thread overview]
Message-ID: <vafvhbtlpea.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "09 Jul 1999 19:06:57 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Hrvoje Niksic <hniksic@srce.hr> writes:
> 
> > Now, if you have a big hole in your article range -- e.g. your article
> > range is 128 - 12300 because you ticked article no. 128 -- total
> > expiry will stat tens of thousands of non-existant files every time 
> > you leave the group.  That tends to get a bit slow.
> 
> One could speed things up by having the backend look at what articles
> exist in the group, and then iterate over that instead of the other
> way around.  That would be much, much quicker for groups with big
> "holes" in them.  It might be slower in other situations, though.

What about having the backend look for the articles actually in the
group, and then intersecting this set with the set of
potentially-to-be-expired articles, then only iterating over that
intersection?

kai
-- 
Life is hard and then you die.


  reply	other threads:[~1999-07-09 17:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-07  1:13 François Pinard
1999-07-07  2:27 ` Hrvoje Niksic
1999-07-07 17:49   ` Rob Browning
1999-07-09 17:06   ` Lars Magne Ingebrigtsen
1999-07-09 17:11     ` Kai.Grossjohann [this message]
1999-07-09 18:20       ` Lars Magne Ingebrigtsen
1999-07-09 17:25     ` François Pinard
1999-07-09 18:26       ` Lars Magne Ingebrigtsen
1999-07-09 22:34         ` Kai.Grossjohann
1999-07-11  9:03           ` Lars Magne Ingebrigtsen
1999-07-12  3:02         ` Hrvoje Niksic
1999-08-27 17:21           ` Lars Magne Ingebrigtsen
1999-08-28 17:55           ` Jan Vroonhof
     [not found]           ` <m3yaexdtre.fsf@quimb <byemgnx00v.fsf@bolzano.math.ethz.ch>
1999-09-25  6:45             ` Lars Magne Ingebrigtsen
1999-07-12 21:16         ` jonkv
1999-07-11 14:13   ` Hallvard B Furuseth

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=vafvhbtlpea.fsf@petty.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).