From: Steinar Bang <sb@metis.no>
Subject: Re: Long time to exit summary buffer, possible speed enhancement?
Date: 30 Sep 1996 07:34:43 +0100 [thread overview]
Message-ID: <whbueomry4.fsf@norne.metis.no> (raw)
In-Reply-To: Hallvard B Furuseth's message of Sun, 29 Sep 1996 14:09:23 +0100 (MET)
>>>>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no>:
> Ken Raeburn <raeburn@cygnus.com> writes:
>> Check for sparse article numbers. I've got some nnml groups where I've
>> ticked some old articles and read (and thus deleted) lots of others with
>> higher numbers. When I check the backtrace as Lars suggests, I find
>> most of the time is spent in the request-expire loop, checking article
>> numbers where all traces of the article have long since been deleted.
>> For example, if you've ticked article 100, and deleted 101-199 months
>> ago, it'll still check 101-199 to see if they exist. I think I brought
>> this up before, during or maybe after the September development cycle.
>> A hack workaround to this is to move all the articles (mark everything
>> with `#', then hit `B m') from the mail group to that same mail group,
>> which causes sequential renumbering and thus removes the empty ranges.
>> Unfortunately, it also discards any xref info if those messages were
>> also stored in other mail groups. And it's only a temporary fix.
> Besides, you can't do that with news articles. An old news article will
> be followed by a *huge* hole in a newsgroup with high voloume and rapid
> expiry, if it is crossposted to a group with slow expiry or if it has an
> Expires: header which makes it stay around for some time.
I too, see this on news articles. It happens mostly on groups with
high traffic and long expiry (ie. the no.* hierarchy. (Thank *God*, I
unsubscribed to no.general)).
next prev parent reply other threads:[~1996-09-30 6:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-27 20:28 Shane Holder
1996-09-28 20:08 ` Lars Magne Ingebrigtsen
1996-09-29 9:50 ` Ken Raeburn
1996-09-30 15:21 ` Shane Holder
1996-09-30 15:51 ` Ken Raeburn
1996-09-29 13:09 ` Hallvard B Furuseth
1996-09-29 21:36 ` Ken Raeburn
1996-09-30 6:37 ` Steinar Bang
1996-09-30 15:57 ` Ken Raeburn
1996-09-30 6:34 ` Steinar Bang [this message]
1996-10-01 3:39 ` Lars Magne Ingebrigtsen
1996-10-01 14:59 ` Colin Rafferty
1996-10-04 10:00 ` Hallvard B Furuseth
1996-10-04 9:54 ` Hallvard B Furuseth
1996-10-01 7:07 ` Kai Grossjohann
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=whbueomry4.fsf@norne.metis.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).