https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6407
--- Comment #3 from Kevin A. McGrail <kmcgr...@pccc.com> 2011-10-29 13:32:05 UTC --- (In reply to comment #2) > The machine has been replaced by a 3.00 GHz XEON so it is now running a bit > faster, but it remains a comparatively slow operation. > The SpamAssassin version is now 3.2.5 and it still exhibits the "slow" > processing per address of a longer list. > > 2.6 seconds of 3 GHz CPU time is an awful lot of processing time for adding an > item to a blacklist database... Add -D to the command. It's compiling and linting, etc. It's not just adding to the DB and running a query. For doing 1 run, it should take start time + a very small amount of overhead per addition. This startup time is the reason for the spamc/spamd pair. Please add -D and time (i.e. time spamassassin -D --add-to-blacklist < file and time spamassassin -D --add-addr-to-blacklist=f...@bar.com) and run for one address vs many and add the output as an attachment to the ticket. My theory is the times will be very close to each other or we'll find something in the debug. Also, what is the backend for your AWL? Perhaps you are getting locking issues or IO bound? Anyway, based on the output, we can decide whether to reopen or move this to the users list as a configuration and administration question. Regards, KAM -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
