https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6046
--- Comment #4 from Michael Alan Dorman <[email protected]> 2009-01-22 06:31:56 PST --- (In reply to comment #3) > What does benchmarking say on auto-purging the database? > In my experience, lengthy auto expiration runs was the single > and most pressing reason to abandon bdb and switch our Bayes > to SQL. Well we don't have to do the dance of move-and-rebuild that DBM does, in part because we are able to create a secondary index on atime that makes it very easy to estimate whether we would expire too many tokens in a given run. So I would expect it to be as efficient as the SQL back-ends in that respect. Still, it's a good question that would not be answered out of the box by the benchmark code, so I've changed the local.cf files in the benchmark directory to remove bayes_auto_expire 0, and I'll re-run and see what the results look like. I'm curious, which SQL back-end are you using? And if it's MySQL, do you have any performance tuning tips? I've been a little startled to find that PgSQL is actually outperforming MySQL on my benchmarks (given their reps) but then I know how to tune PgSQL well; I'm more ignorant about MySQL. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
