Roland Rosenfeld wrote: > > The triplet table currently contains 5.5M entries and every hour ~250k > entries are expired. Without maintenance this took some minutes now. > So I tried a "mysqlcheck -r" on the database (which took only two > minutes) and after this cleanup runs much faster.
5.5M entries should be no problem and even with 10M entries, your cleanup should be occurring fairly quickly. >> You also didn't mention what version of mySQL DB you were running. > > 5.0.51a Policyd was test/written for MySQL 4.x. This doesn't mean it shouldn't behave the same for v5. Unless i'm mistake (or things have changed between versions), using "DELETE QUICK" on an auto-incrementing row is where holes (/fragmentation) occurs. This was one of the reasons that Policyd has no auto-incrementing fields. Is this no longer the case with MySQL v5? > Also the syslog output is broken, because the timestamps > are created by syslogd, which writes to disk nearly a minute after the > event happened (had to patch cleanup, now it writes its own timestamps > to the log instead of syslog). You shouldn't have to patch cleanup. What is the output of: # cat /etc/syslog.conf | grep mail Cami ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
