[ZODB-Dev] Relstorage and over growing database.

Juan A. Diaz nueces at ravvit.net
Sun Feb 3 03:40:46 UTC 2013


2013/2/2 Shane Hathaway <shane at hathawaymix.org>:
> On 02/02/2013 04:13 PM, Juan A. Diaz wrote:
>>
>> 2013/2/2 Shane Hathaway <shane at hathawaymix.org>:
>>>
>>> On 02/01/2013 09:08 PM, Juan A. Diaz wrote:
>>
>> Do you think that add one option in zodbpack to truncate this tables
>> after the pack could be a god idea?
>
>
> The object_ref table is intended to help the next pack run quickly, but I
> suppose it might make sense to clear it anyway with an option.

Ok, I going to try implement it in the next week, and send a pull request :)

>>> If your database grows by 2.2 GB per day, it's not surprising that the
>>> database is 15 GB.  With drive and RAM sizes today, 15 GB doesn't sound
>>> like
>>> a problem to me... unless it's on a Raspberry Pi. :-)
>>
>>
>> Yes, but after the pack the size of new objects that remain in the
>> database is just like 200MB.
>>
>> Also 15GB as you say is not a real big database for this days, but we
>> are synchronizing our databases through a low bandwidth channel across
>> various datacenters and in some cases recover the database from a
>> failure in the sync process is real pain!. Do you think that is
>> possible to don't replicate that tables could be safe? There are other
>> tables that maybe we don't need replicate?
>
>
> You never need to replicate the MyISAM tables.  Only the InnoDB tables
> (object_state, current_object, transaction) need to be replicated.

Perfect!

> Shane
>

Thank again for you time =)

Cheers.

nueces...


More information about the ZODB-Dev mailing list