>
> > . Implement db transparent compression (that what I'm doing, first release
> > 4 August, benchmark results 5 August
>
> Does this recognize already-compressed data? I didn't think about this
> earlier, but the excerpts are *supposed* to be using the HtZlibCodec
> since they're large enough to get significant benefit.
>
The compression can be done on a per base basis. I.e. you can compress
if you expect a win or not compress if you don't.
If the excerpts are compressed, then the base that contains them can be
a regular base, not using transparent Berkeley DB compression.
> > . Upgrade to db-2.7.5
>
> I don't really consider this a goal. Part of a move towards a release
> entails updating code from external sources to the latest version. This
> includes a variety of files in htlib/ from glibc as well as the db code.
> By the time we have a 3.2 release, the versions will likely be
> different.
The only motive to upgrade to db-2.7.5 is that the transparent I/O
compression patch I did applies to it.
Cheers,
--
Loic Dachary
ECILA
100 av. du Gal Leclerc
93500 Pantin - France
Tel: 33 1 56 96 09 80, Fax: 33 1 56 96 09 61
e-mail: [EMAIL PROTECTED] URL: http://www.senga.org/
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
