[EMAIL PROTECTED] wrote:
>        One of the things I tried is to check the efficiency of
> prefix compression. But I can't make it work. db_stat constantly
> says that no prefix saving occurs despite the fact that my 500 000

I reported this to Sleepycat a long time ago because I wondered if we
were doing prefix compression when it reported nothing saved. They
reported that it's a known bug in db_stat. In fact, the version I
compiled from the CVS tree no longer reports prefix compression
statistics (I guess as a "workaround"):

0x53162 Btree magic number.
6       Btree version number.
Flags: DB_DUP
2       Minimum keys per-page.
4096    Underlying tree page size.
2       Number of levels in the tree.
22063   Number of keys in the tree.
1       Number of tree internal pages.
175     Number of tree leaf pages.
86      Number of tree duplicate pages.
0       Number of tree overflow pages.
0       Number of pages on the free list.
420     Number of bytes free in tree internal pages (90% ff).
268614  Number of bytes free in tree leaf pages (63% ff).
0       Number of bytes free in tree duplicate pages (100% ff).
0       Number of bytes free in tree overflow pages (0% ff).

> of a db_stat on a file of yours that shows that prefix compression
> indeed work. I'd be even more gratefull if you said 'ha, ha, there
> is a trick, you must be carefull to do the following ....'. BTW,

No trick. If you don't specify a prefix comparison function (we don't)
it does it automatically, considering keys as (char *). At least that's
what they tell me. Judging from the size of the databases, I believe
them.

> I'm using Database.h interface to create and manipulate the db
> file when runing the benches.

You should probably be using some form of DB2_db.cc, either through the
Database code or directly. But I think that's what you meant.

-Geoff

------------------------------------
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.

Reply via email to