Andrea Brancatelli wrote:
<snipped a very detailed explanation> Summarizing everything: - If you have a single DB server: use a shared InnoDB tablespace preallocating the space and disabling the autoextend. Using the optimize table will give you a better optimization of the tables, and you'll have no problem with the space as it's already allocated up to a fixed size - If you have a machine with various tasks going on, like a mail server, web server, db server and whatever, use the innodb_file_per_table. Usigon the optimize table you'll reclaim your space back whenever you delete anything or whenever any table will significantly decrease in size. Doubt? Question? Fear? Panic?
Excellent writeup! So basically it helps avoid juggling around 50GB+ files. One question though - does it make any difference in performance? You said that you have not done any benchmarking - did anyone else on the list? When one has 15GB of email, performance counts.
_______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
