ktm <at> rice.edu wrote: > We currently use a SQL purge that is adjusted to only process a subset of the > users per query. We use the first letter of the user name, but anything that > partitions the query into smaller pieces will work. The actual DB > partitioning > allows maintenance to work on smaller pieces at a time, but that will be an > optimization we are including when we update.
Hello, we made a table optimization and now purge-maintenance has greatly improved. I also switch to TOE, it seems this is really good and I will evaluate how db size will change. In future we could consider to: * reduce range of users per query. * implement native mysql partitioning. But in this case it seems we should back to MyISAM to improve partitioning. Uhm... * limit dspam to users who really want to retrain. Thank you very much for all hints Marco ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
