On Jul 21, 2010, at 3:16 PM, Paul Cockings wrote: > Current MySQL DB: > > dspam_signature_data InnoDB 422 K rows 2.28GB > dspam_token_data InnoDB 21.52 M rows 5.14GB
Now that is interesting. I had originally set up my dspam config with InnoDB tables under the theory that row-level locking would end up being more performance in an email environment than table-level. InnoDB ended up being so slow that the pages would time out, even under the incredibly low load of my personal email machine, so I reverted them to MyISAM a year or so ago and that really sped things back up. Have you done anything special to get InnoDB to perform, other than the typical MySQL buffer tweaking and stuff? Or is 3.9.0 just that much faster? - Mark ----- m...@pdc-racing.net ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
