[TYPO3-english] big cachingframework tables

Richard Davies richard at ocular.co.nz
Wed Jan 11 09:15:48 CET 2012


Hi,

Mysql has some flaws. http://bugs.mysql.com/bug.php?id=1341. The best way
to save the space is to dump ALL your tables, delete the database files and
and reload your files.

http://mysqlhacker.com/kabir/innodb/reclaiming-your-innodb-tablespace.html

Richard

On 11 January 2012 19:09, Katja Lampela <katja.lampela at lieska.net> wrote:

> Hi,
>
> 9.1.2012 17:18, Dmitry Dulepov kirjoitti:
>
>  Xavier Perseguers wrote:
>>
>>> There's a scheduler task that you should run regularly.
>>>
>>
>> Just checked the scheduler job. It will remove records from the table but
>> it will not make disk usage smaller because InnoDb does not reuse the disk
>> space. New records for InnoDb are added to the end of the existing space,
>> even if that space is not used. In other words, the task will make
>> phpMyAdmin show less space for the table but it will not decrease actual
>> disk space.
>>
>
> Thank you Dmitri. Does this mean there is no way to optimize disc usage in
> this sector? So that even if the site would reduce in size, the db keeps
> growing (concerning InnoDb)? That would be really odd. Or maybe I'm missing
> some obvious server setting here (I have the innodb_file_per_table option
> on).
>
>
> --
> With kind regards
>
> Katja Lampela
> *Lieska-tuotanto*
> www.lieska.net
>
> ______________________________**_________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-**bin/mailman/listinfo/typo3-**english<http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english>
>


More information about the TYPO3-english mailing list