Geert Hendrickx wrote: >> Some companies have heavily loaded databases so in order to minimize >> downtime they run the cleanup script weekly. > > In case you're only using whitelisting+greylisting (as we are, ATM), doing > the auto-whitelisting asynchronously takes aways 1/3rd of the queries for > each policyd request.
Amount of queries really aren't an issue, the queries are light-weight and fully indexed. > Granted, the cleanup run will be heavier, but those can be scheduled in > off-peak hours. Heavier? ;) You're talking about an exceptionally heavier query since there would be comparisons done for *every* triplet whos threshold matches the auto-whitelisted count. The triplet is already being checked, so use that information instead of having to re-query the same data later. >> I guess if there was a demand for it, it could be user-configurable. >> Patches will be accepted if there is a demand for it. > > Alternatively, the deletes of auto-whitelisted triplets could be postponed > to the cleanup script? That really does not save again, instead it makes the cleanup script take far longer to process. What problem are you trying to solve? This method is running under very large isp's (+700 000 mailboxes) and the MySQL server is doing just fine. Cami ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
