Hi, this question is mainly for Mark and amavisd-new developers. Memory refresh: here we deal with a huge 72GB 30-day MySQL quarantine which is constantly growing. Main problem is daily maintenance which is taking A LOT (delete 1-day stuff now takes about 12 hours).
We might be a bit on the high side of amavisd-new users, but given current trends I would not be surprised other setups will soon face cleanup problems. So the question is: how hard would it be to patch/modify amavisd-new code to support per-day or per-week msgs/msgrcpt/quarantine tables? Let's take per-week. On the RDBMS we create msgs01..msgs52 msgrcpt01..msgrcpt52 and quarantine01..quarantine52. Depending on the week of the year amavisd-new fills different tables. Cleanup is just a matter of DROP and CREATE 3 tables rather than long SELECT/DELETE queries. Moreover we don't rely on InnoDB space reuse capabilities but offer fresh new tables. The maddr table remains unchanged (we're not cleaning it up anyway). I am not a threaded-Perl programmer, so I wonder how much overhead such a change would impact the current code. Would we need a full stop-restart cycle or just to propagate a SIGxyz? Obviously quarantine management software would need to change lookup queries, but I doubt large sites actually use such software. TIA, Paolo -- | www.paolocravero.tk + IQRP #476 + skype://pcravero | | SpamAssassin-based email antispam/antivirus solutions | \ Italian/English-to/from-Croatian translations / ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
