Gnus development mailing list
 help / color / mirror / Atom feed
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Cc: ding@ifi.uio.no
Subject: Re: Long time to exit summary buffer, possible speed enhancement?
Date: Sun, 29 Sep 1996 14:09:23 +0100 (MET)	[thread overview]
Message-ID: <199609291309.OAA29461@gandalf.uio.no> (raw)
In-Reply-To: <w8s684yl7wt.fsf@ylfing.ifi.uio.no>

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
>Shane Holder <holder@mordor.rsn.hp.com> writes:
> 
>> Would it be possible to make gnus understand that if an
>> article doesnt exist that it can collapse the range?
> 
> Well, it can't -- then the range would be incorrect, wouldn't it?

Why, no.  Articles get increasing numbers as they arrive.  They will not
not interleave.  Hmm - except if the article number wraps around.  That
can happen, right?  So *big* holes in ranges must not be collapsed since
new articles may be arriving at the beginning of the hole.  Instead,
nonexisting article numbers should be removed from the beginning of a
range following a big hole, to make room for new articles.

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> Anyways, range handling isn't all that slow, so the ~10 second delay
> probably is caused by something else.  Try `(setq debug-on-quit t)'
> and then `C-g' when things "hang" (sorta).  The resulting backtrace
> should tell you which function is being slow.

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.


Regards,

Hallvard


  parent reply	other threads:[~1996-09-29 13:09 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 [this message]
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
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=199609291309.OAA29461@gandalf.uio.no \
    --to=h.b.furuseth@usit.uio.no \
    --cc=ding@ifi.uio.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).