Yes you can proceed easily with those two settings and have a first bigger improvement.
If you're switching away from dbmail I wouldn't go trough the hassle of upgrading, since the upgrade need to reparse all the message to use the de-deduplication features. Note: the ALTER TABLE will perform the OPTIMIZE TABLE, so you don't need to run the two commands, just go for the ALTER TABLE. --- Andrea Brancatelli Schema31 S.p.a. Responsabile IT ROMA - BO - FI - PA ITALY Tel: +39. 06.98.358.472 Cell: +39 331.2488468 Fax: +39. 055.71.880.466 Società del Gruppo SC31 ITALIA Il 2016-03-02 21:36 Simon Buchanan ha scritto: > Further to this - sorry i just looked at the archive and saw the "[Dbmail] > database overhead" subject that has been discussed just recently... > > We have "innodb_file_per_table = 1", so am i correct that i should run > "optimize table" on all the tables, then also enable InnoDB Barracuda and do > an ALTER TABLE Engine=InnoDB ROW_FORMAT=COMPRESSED? > > Thanks > > Simon > > On 3 March 2016 at 9:30:50 AM, Simon Buchanan (grem...@gmail.com) wrote: > >> Hi All, >> >> We are running dbmail 2.2.18 for some legacy clients, the database is a >> debian default 5.1.73. We have around 260 mailboxes on this server that >> (when dbmail-export'ed) comprise of 72G of data, or approx 280MB per mailbox >> on average. We are running "/usr/local/sbin/dbmail-util -ay" every morning >> at 3am. >> >> The problem we have is that the mysql data store is around 680G with the >> dbmail_messageblks.ibd file being the culprit at 654G. >> >> Is there any way to claw back this space? >> >> Thanks! >> >> Simon > > _______________________________________________ > DBmail mailing list > DBmail@dbmail.org > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
