Re: [AMaViS-user] a new discovery

Grant,

> > the way i discovered this was that I was looking for a way to
> > determine how long each test takes. I've looked at the TIMING lines
> > in the log which say that SA-Check is 98% all the time. I want to
> > break that down further and see if there are checks which I am
> > running which take a silly amount of time and/or do not need to be
> > run because they never get a hit.
> >
> > Q2 Is this possible and/or sensible.

Mike writes:
| Yes, you can. You may need to either increase log_level (I use
| $log_level = 2), or set

This does not achieve what Grant has in mind I believe, i.e. a timing
breakdown of operations within SpamAssassin. Unfortunately SA does not
(yet) offer such information. One possibility is to take a sample mail,
and feed it to a command line spamassassin (as user vscan) with a -D option
for debugging, then timestamp each debug line. Ignoring the startup and
initialization cost (which is factored out when SA is called from amavisd),
the rest of SA test performance should be about the same as if SA were
called from amavisd.

Mark

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/...fo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/