Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: performance of fuzzy subject handling and killing threads
Date: 24 May 1996 17:41:51 +0200	[thread overview]
Message-ID: <x6k9y23wov.fsf@eyesore.no> (raw)
In-Reply-To: Ken Raeburn's message of Fri, 24 May 1996 06:24:51 -0400

Ken Raeburn <raeburn@cygnus.com> writes:

> Since the simplified strings come out the same each time they're
> generated, I figured, why not cache them?  It'll slow down the first
> pass through the article list a little, but following passes should be
> much faster.  And in newsgroups with lots of unread articles -- enough
> for the additional cost of building the cache to be noticeable -- I'm
> guessing it's probably not the most common case that 'k' gets used
> exactly once.

Yes, I never use `k' myself.  (Well, I just use `M-C-l' to kill
articles; what with the threading and gathering, it kills exactly the
same articles that `k' does in a fraction of the time.)

> And while I'm at it, why not intern them in a group-local obarray?
> That way emacs itself would automatically keep them unique, so
> comparisons would be even cheaper, and the extra storage required
> would be reduced somewhat in most cases.

Nice technique.  I'll be adding your stuff to Red Gnus.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


  reply	other threads:[~1996-05-24 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-24 10:24 Ken Raeburn
1996-05-24 15:41 ` Lars Magne Ingebrigtsen [this message]
1996-05-24 18:17   ` Jack Vinson
1996-05-24 18:44     ` Lars Magne Ingebrigtsen
1996-05-24 20:58   ` Ken Raeburn
1996-05-24 21:21     ` Lars Magne Ingebrigtsen

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=x6k9y23wov.fsf@eyesore.no \
    --to=larsi@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).