Uwe Kiewel wrote: > Hi there, > > I know, Paul is on holiday. > > But in relation to Jorges "db growing size" thread: > > Is it an option to include the "OPTIMIZE TABLE" parts into the code of > dbmail-util? Let's discuss about advantages and disadvantages! >
Placing this functionality in dbmail-util would suggest that it is ok to run this daily/weekly/what have you, and I'd say this is an extremely bad idea. As someone said earlier in Jorge's thread this is a task for the DBA, not for the dbmail admin. My dataset size is 25GB, and an OPTIMIZE on the messageblocks takes about 2 hours on a dedicated server. The entire table is under an exclusive lock during this time[1], which renders the entire suite (both insertion and IMAP/POP access) stall with timeouts. Besides, specifically for Innodb running with file_per_table=1 (which is what everyone should do anyway), the OPTIMIZE TABLE statement doesn't do much. The first (and only) time I ran it was 10 months after deploying my setup, and it saved me a total of 250M, out of roughly 28G. The total downtime was about 4 hours (I did this at night). Clearly nothing to gain here. My 2c Peter [1] http://dev.mysql.com/doc/refman/5.0/en/optimize-table.html _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
