Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@metis.no>
Subject: Re: Huge groups
Date: 22 Jan 1998 17:38:41 +0100	[thread overview]
Message-ID: <when20ihv2.fsf@norne.oslo.metis.no> (raw)
In-Reply-To: Lars Syrstad's message of "22 Jan 1998 12:28:49 +0100"

>>>>> Lars Syrstad <lars@no482rs1.aventura.no>:

>> (I suspect that with the current backend interface this won't give any
>> speedups, since Gnus needs to hold the entire Summary buffer
>> information in memory to do the threading and scoring and stuff. And
>> even without doing any sort of profiling I'm gueesing that there is a
>> performance bottle neck here)

> Any reason why the necessary information to do threading and scoring
> could not go into the Overview-file, which in turns goes into a DBM
> file?

The necessary information is there already.  I just think that the
bottleneck is after this information has been turned into lisp lists
so that Gnus can process it, not in the file format itself, and not in
the reading and the parsing of the .overview file format.

But I haven't profiled anything, so I'm just guessing at this.


  reply	other threads:[~1998-01-22 16:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-20  4:01 Matt Simmons
1998-01-20  4:19 ` SL Baur
1998-01-20  7:15 ` Jason L Tibbitts III
1998-01-20  7:39   ` Steinar Bang
1998-01-20  9:29     ` Jason L Tibbitts III
1998-01-21 14:32       ` Stefan Waldherr
1998-01-21 14:48         ` Hrvoje Niksic
1998-01-22 10:31         ` jari.aalto
1998-02-08 15:22           ` Re: Lars Magne Ingebrigtsen
1998-01-20 10:32   ` Huge groups Jan Vroonhof
1998-01-21  0:58     ` Jason L Tibbitts III
1998-01-21 12:59       ` Steinar Bang
1998-01-22 11:28         ` Lars Syrstad
1998-01-22 16:38           ` Steinar Bang [this message]
1998-01-23 10:38             ` Lars Syrstad
1998-01-23 15:34               ` Steinar Bang
1998-02-08 15:24               ` Lars Magne Ingebrigtsen
1998-01-22 18:41         ` David Aspinwall

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=when20ihv2.fsf@norne.oslo.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).