public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: "Frank Ch. Eigler" <fche@cygnus.com>
Cc: Jason Molenda <jason-swarelist@molenda.com>,
	Chris Faylor <cgf@cygnus.com>,
	overseers@sourceware.cygnus.com
Subject: Re: htdig, was Re: cygwin-xfree
Date: Sat, 30 Dec 2000 06:08:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.10.10005060502130.11960-100000@dair.pair.com> (raw)
In-Reply-To: <20000503232313.A29536@cygnus.com>

On Wed, 3 May 2000, Frank Ch. Eigler wrote:
> For the htdig databases, adding "compression_level: 9"
> to htdig.conf should reduce the disk space usage by about 20%.

Tests show that the db.docdb "before merging" went from 324231168 to
180889600 bytes, so I made that change for the gcc installation.  It
is running its normally scheduled update right now, but from scratch
today to save extra.  Doh, I just think I should have thought about that
long ago.

For the curious (but not curious enough to read up) this uses zlib to
individually compress each "document head"; the text that shows up for
each search hit.  FWIW, in 2.0 compression will be done at the DB level,
which would be the right thing.

If nothing broke (I'm cautious sometimes :-) we can move that conf item 
from gcc.conf to site.conf.

> Also, the rundig scripts use htdig's "-i" option (causing the
> databases to be regenerated from scratch),

No, since we don't use the basic rundig, as Jason told you.

> the "db.wordlist"
> files may be deleted after each search, saving another 30%.

No, it's needed when you do an "update" (not running from scratch).

Thanks!

brgds, H-P

WARNING: multiple messages have this Message-ID
From: Hans-Peter Nilsson <hp@bitrange.com>
To: "Frank Ch. Eigler" <fche@cygnus.com>
Cc: Jason Molenda <jason-swarelist@molenda.com>,
	Chris Faylor <cgf@cygnus.com>,
	overseers@sourceware.cygnus.com
Subject: Re: htdig, was Re: cygwin-xfree
Date: Sat, 06 May 2000 02:43:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.10.10005060502130.11960-100000@dair.pair.com> (raw)
Message-ID: <20000506024300.1caIzM5XuodlO_MNlR902kiQzeWynChhcepMGx4bOfo@z> (raw)
In-Reply-To: <20000503232313.A29536@cygnus.com>

On Wed, 3 May 2000, Frank Ch. Eigler wrote:
> For the htdig databases, adding "compression_level: 9"
> to htdig.conf should reduce the disk space usage by about 20%.

Tests show that the db.docdb "before merging" went from 324231168 to
180889600 bytes, so I made that change for the gcc installation.  It
is running its normally scheduled update right now, but from scratch
today to save extra.  Doh, I just think I should have thought about that
long ago.

For the curious (but not curious enough to read up) this uses zlib to
individually compress each "document head"; the text that shows up for
each search hit.  FWIW, in 2.0 compression will be done at the DB level,
which would be the right thing.

If nothing broke (I'm cautious sometimes :-) we can move that conf item 
from gcc.conf to site.conf.

> Also, the rundig scripts use htdig's "-i" option (causing the
> databases to be regenerated from scratch),

No, since we don't use the basic rundig, as Jason told you.

> the "db.wordlist"
> files may be deleted after each search, saving another 30%.

No, it's needed when you do an "update" (not running from scratch).

Thanks!

brgds, H-P

  parent reply	other threads:[~2000-12-30  6:08 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 cygwin-xfree Chris Faylor
2000-05-03 19:18 ` cygwin-xfree Chris Faylor
2000-12-30  6:08 ` cygwin-xfree Tom Tromey
2000-05-03 19:59   ` cygwin-xfree Tom Tromey
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 20:07     ` cygwin-xfree Chris Faylor
2000-12-30  6:08     ` cygwin-xfree Tom Tromey
2000-05-03 20:09       ` cygwin-xfree Tom Tromey
2000-12-30  6:08       ` cygwin-xfree Chris Faylor
2000-05-03 20:22         ` cygwin-xfree Chris Faylor
2000-12-30  6:08         ` cygwin-xfree Jim Kingdon
2000-05-04  4:52           ` cygwin-xfree Jim Kingdon
2000-12-30  6:08           ` cygwin-xfree Chris Faylor
2000-05-04  7:48             ` cygwin-xfree Chris Faylor
2000-12-30  6:08         ` cygwin-xfree Bob Manson
2000-05-03 21:11           ` cygwin-xfree Bob Manson
2000-12-30  6:08           ` cygwin-xfree Jason Molenda
2000-05-04 13:19             ` cygwin-xfree Jason Molenda
2000-12-30  6:08             ` cygwin-xfree Stan Shebs
2000-05-21 22:19               ` cygwin-xfree Stan Shebs
2000-12-30  6:08               ` cygwin-xfree Mark Galassi
2000-05-22  6:15                 ` cygwin-xfree Mark Galassi
2000-12-30  6:08             ` cygwin-xfree Jim Kingdon
2000-05-07  6:32               ` cygwin-xfree Jim Kingdon
2000-12-30  6:08       ` libstdc++-v3 things that still are not working correctly Benjamin Kosnik
2000-05-03 20:14         ` Benjamin Kosnik
2000-12-30  6:08         ` Jeffrey A Law
2000-05-03 22:33           ` Jeffrey A Law
2000-12-30  6:08     ` cygwin-xfree Per Bothner
2000-05-03 23:21       ` cygwin-xfree Per Bothner
2000-12-30  6:08       ` cygwin-xfree Jim Kingdon
2000-05-04  4:35         ` cygwin-xfree Jim Kingdon
2000-12-30  6:08 ` cygwin-xfree Jeffrey A Law
2000-05-04  9:07   ` cygwin-xfree Jeffrey A Law
2000-12-30  6:08 ` cygwin-xfree Andrew Cagney
2000-05-03 19:30   ` cygwin-xfree Andrew Cagney
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 19:34     ` cygwin-xfree Chris Faylor
2000-12-30  6:08   ` cygwin-xfree Jim Kingdon
2000-05-03 19:47     ` cygwin-xfree Jim Kingdon
2000-12-30  6:08 ` cygwin-xfree Jason Molenda
2000-05-03 19:45   ` cygwin-xfree Jason Molenda
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 19:53     ` cygwin-xfree Chris Faylor
2000-12-30  6:08   ` htdig, was cygwin-xfree Frank Ch. Eigler
2000-05-03 20:23     ` Frank Ch. Eigler
2000-12-30  6:08     ` Hans-Peter Nilsson [this message]
2000-05-06  2:43       ` Hans-Peter Nilsson

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=Pine.BSF.4.10.10005060502130.11960-100000@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=cgf@cygnus.com \
    --cc=fche@cygnus.com \
    --cc=jason-swarelist@molenda.com \
    --cc=overseers@sourceware.cygnus.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).