Kolab 3.4 - Apache mem usage and mysql db grow

[Markelov Alexander]

Table Optimize doesn't work for InnoDB
"Table does not support optimize, doing recreate + analyze instead"

I had recreated MySQL Tables in InnoDB File-Per-Table Tablespaces - 
http://dev.mysql.com/doc/refman/5.0/en/innodb-multiple-tablespaces.html
After that I can reclaim disk space.
I have done it's on my backup-server.
Why Kolab don't expunge own cache by default?

13.03.2015 11:45, Markelov Alexander пишет:
>
>
> 13.03.2015 11:31, Aleksander Machniak пишет:
>> On 03/13/2015 08:50 AM, Markelov Alexander wrote:
>>> After upgrade to new Kolab 3.4, I noticed a few things:
>> Which distro?
> Debian 7.8
>>> 1. apache2.prefork processes have a lot of memory usage. All 32Gb 
>>> mem of
>>> host is used.
>> Does apache restart help and for how long?
> Yes. It's help for about 24 hours.
>>> 2. Mysql database is growing very fast. File ibdata1 is 245Gb now.
>> Which tables are the biggest, which tables grow?
> After some investigation:
> db - roundecube
> Tables:
> kolab_cache_contact - 13.5 GiB
> kolab_cache_events - 223.4 GiB
> kolab_cache_note - 2.5 GiB
> kolab_cache_task - 1.3 GiB
>
> I had founded plugins/libkolab/bin/modcache.sh in 
> /usr/share/roundcubemail/ and try to expunge caches on the backup 
> server. But as I can see I need to do Optimize table for free space on 
> the storage.
>

-- 
Markelov Alexander - IT/Net engineer
http://13.net.ru
xmpp:deep at 13.net.ru
ICQ 13372829