Olly
[ RSS | ATOM 1.0 ]
Powered by PyBlosxom

« Low-Hanging Key Size Reduction | Home | Gmane Size Analysis Update »

Low-Hanging Key Size Reduction Results

To summarise my previous entry, my calculations predicted a size reduction of around 8.61GB, with the expectation that it would probably be a little larger due to second-order savings not being accounted for.

The conversion utility has now finished running, and the actual saving is 8.73GB, which is 2.5% of the database size.

Table Before (KB) After (KB) Reduction (KB) Saving
spelling 75,360 75,360 0 0%
record 20,725,220 20,658,724 66,496 0.32%
postlist 56,457,616 55,382,492 1,075,124 1.90%
termlist 69,131,224 69,040,416 90,808 0.13%
position 216,759,520 208,832,488 7,927,032 3.66%

There are no changes to the spelling keys, hence there's no size change there. The position table has a lot of small entries, so benefits most. And the postlist table benefits from the improvements to both the uint and string encodings, so does next best.


Posted in xapian by Olly Betts on 2009-12-16 22:52 | Permalink


« Low-Hanging Key Size Reduction | Home | Gmane Size Analysis Update »