[Zope-dev] Re: Zcatalog bloat problem (berkeleydb is a solution?)

[Giovanni Maruzzelli]

I'm sorry to say that Toby is right in pointing at the version from which I
cutted and pasted the following, but we are using also a newer version and
the problem is the same.

We're working out our way with the "dump the first bytes of the raw dump" of
the new, magnificent tranalyzer from Toby (it reallly ought to be a standard
tool in the Zope distro), and we have now some hints of what happen when you
catalog something.

So, we are starting to optimize indexes and metadata, but the problem seems
not to fade away.

-giovanni


----- Original Message -----
From: "Toby Dickenson" <tdickenson@devmail.geminidataloggers.co.uk>
To: "Giovanni Maruzzelli" <maruzz@open4.it>
Cc: "Chris McDonough" <chrism@digicool.com>; <a.deuring@satzbau-gmbh.de>;
<zope-dev@zope.org>; <erik@thingamy.net>; <barry@digicool.com>;
<tdickenson@geminidataloggers.com>; <tsarna@endicor.com>
Sent: Tuesday, June 26, 2001 5:49 PM
Subject: Re: [Zope-dev] Re: Zcatalog bloat problem (berkeleydb is a
solution?)


> >INDEXES:
> >  PrincipiaSearchSource Text Index 2,524
> >  autore Keyword Index 4,055
> >  bflow0 Field Index 4,055
> >  bflow1 Field Index 4,055
> >  bflow2 Field Index 4,055
>
>
> Aha! a clue.
>
> If that is the output of the 'Indexes' tab then I dont think you are
> using the newest ZCatalog. A recent release (im not surwe which,
> 2.3.2?) has a new BTree implementation that reduces bloat by modifying
> fewer buckets (it also doesnt have the column showing index size)
>
> Toby Dickenson
> tdickenson@geminidataloggers.com