[ Apologies if this already appeared; I don't see it in the archives. ] Howdy,
Just upgraded to 2.60, seems to work great for the most part! Catching even more spam than before (as to be expected). One thing which has become a bit of a problem - AWL seem to be much slower in some cases, although I'm not sure why. My AWL is currently 146M, so it's pretty hefty. I've just moved it out of the way for the moment, and we're back up to speed. When things are slow, one process grabs a lock and then takes 40-50 seconds to do its work. A truss shows lots of "read()" going on the DB file. Is there a place in the code where sequential scans or other nasties are happening? Perhaps when the AWL is updated, as opposed to merely referenced? DB_File should be fast and not doing this type of access; it's actually performing enough I/O to max the disks out. Any pointers/debugging to do, please let me know! Thanks, David. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
