Dear ZODB developers,
Since some time ago (not sure since when) our database
has passed from 15GB to 65GB so fast, and it keeps growing
little by little (2 to 5 GB per day). It is clear that something is not
correct in it.
We would like to check which objects are taking most of the space
or just
2009/12/7 Jose Benito Gonzalez Lopez :
> Dear ZODB developers,
>
> Since some time ago (not sure since when) our database
> has passed from 15GB to 65GB so fast, and it keeps growing
> little by little (2 to 5 GB per day). It is clear that something is not
> correct in it.
>
> We would like to chec
On Mon, Dec 7, 2009 at 8:31 AM, Jose Benito Gonzalez Lopez
wrote:
> Since some time ago (not sure since when) our database
> has passed from 15GB to 65GB so fast, and it keeps growing
> little by little (2 to 5 GB per day). It is clear that something is not
> correct in it.
Are you packing it reg
Hello all,
> Since some time ago (not sure since when) our database
> has passed from 15GB to 65GB so fast, and it keeps growing
> little by little (2 to 5 GB per day). It is clear that something is not
> correct in it.
>
I'd just like to add that there's some changes that can be related to this
> I'd just like to add that there's some changes that can be related to this:
>
> - we had some classes inheriting from Persistent that now inherit from
> something else as well (but no extra arguments are being added, AFAIK);
> - we added some zope.interface definitions to some Persistent classes;
Guys,
Thanks for all the great feedback. Still processing it but here are
somethings we will try.
RelStorage - in our app context to see if there it helps / hurts. will
report back results. Quick tests show some improvement. We will also
look at tuning out current ZEO setup. Last time I
On Dec 7, 2009, at 11:08 AM, Erik Dahl wrote:
...
> Our slow loading object was a persistent with a regular list inside of
> the main pickle. Objects that the list pointed to were persistent
> which I believe means that hey will load separately. In general we
> have tried to make our per
On Mon, Dec 7, 2009 at 11:08 AM, Erik Dahl wrote:
> Guys,
>
> Thanks for all the great feedback. Still processing it but here are
> somethings we will try.
>
> We will also
> look at tuning out current ZEO setup. Last time I looked there was
> only the invalidation queue. I poked around a bit f
On Mon, Dec 7, 2009 at 11:00 AM, Alan Runyan wrote:
...
> A design pattern for RDBMS is to have 2 pools. READ pool and WRITE pool.
> Often the READ pool comes from some replica and WRITE is to the master.
> I'm unsure this pattern would work for ZODB. I know Malthe was thinking
> about this but u
On 12/07/2009 05:00 PM, Alan Runyan wrote:
>> I'd just like to add that there's some changes that can be related to this:
>>
>> - we had some classes inheriting from Persistent that now inherit from
>> something else as well (but no extra arguments are being added, AFAIK);
>> - we added some zope.i
On 2009-12-7 17:34, Jim Fulton wrote:
> On Mon, Dec 7, 2009 at 11:00 AM, Alan Runyan wrote:
> ...
>> A design pattern for RDBMS is to have 2 pools. READ pool and WRITE pool.
>> Often the READ pool comes from some replica and WRITE is to the master.
>> I'm unsure this pattern would work for ZODB.
Biggest DBs we see are in the 10GB range. Most are significantly
smaller (100s of MB) so I don't think size is an issue. We typically
run big persistent caches so I don't think there is much help to be
had there. It would only make reads faster anyway right?
-EAD
On Dec 7, 2009, at 11:
Hi,
Actually, we have two different versions (current and beta) of the software,
working against the same ZODB. We are just developing new features
on top of the beta version.
Fearing that it was due to some changes done by a programmer
we have disabled the "beta version" but the growing of the D
On Mon, Dec 7, 2009 at 3:08 PM, Jose Benito Gonzalez Lopez
wrote:
> Hi,
>
> Actually, we have two different versions (current and beta) of the software,
> working against the same ZODB. We are just developing new features
> on top of the beta version.
> Fearing that it was due to some changes don
On Mon, Dec 7, 2009 at 1:46 PM, Erik Dahl wrote:
> Biggest DBs we see are in the 10GB range. Most are significantly smaller
> (100s of MB) so I don't think size is an issue. We typically run big
> persistent caches so I don't think there is much help to be had there. It
> would only make reads
Hi Jose
> Betreff: Re: [ZODB-Dev] Data.fs size grows non-stop
>
> Hi,
>
> Actually, we have two different versions (current and beta)
> of the software, working against the same ZODB. We are just
> developing new features on top of the beta version.
> Fearing that it was due to some changes d
i would think it would be more useful immediately to account for the rate of
growth rather than trying to account for all objects in the zodb. i've
attached a quick script you can use to get some introspection on the last
few transactions of a large data.fs file. it operates in read only mode,
just
> Have you tried packing the database?
>
Pack has just finished: 17GB.
Still a lot, some months ago was 6GB
> I recommend buying a bigger disk -- seriously, before you run out of space. :)
>
yes, but by the time the bigger disk arrives...we will be done :)
BTW Jim, your class_stats has
Jose Benito Gonzalez Lopez wrote:
> Dear ZODB developers,
>
> Since some time ago (not sure since when) our database
> has passed from 15GB to 65GB so fast, and it keeps growing
> little by little (2 to 5 GB per day). It is clear that something is not
> correct in it.
>
> We would like to check w
19 matches
Mail list logo
