The requirement for timing can be requested by a application using
the SpamAssassin library. Currently amavisd does turn it on and
the SpamAssassin timing report is included in the amavisd log,
but the spamd does not include the timing report in its log.
On 2015-05-05 1:20, Kevin A. McGrail wrote:
Neat. Can you cut and paste an example log and perhaps we can mimic it
in spamd easily?
Here's and example
(I hope my mailer won't wrap it unnecessarily):
May 5 01:34:51 dorothy amavis[8286]: (08286-06) TIMING-SA [total 2178
ms, cpu 2
89 ms] - parse: 0.87 (0.0%), extract_message_metadata: 13 (0.6%),
get_uri_detail
_list: 0.65 (0.0%), tests_pri_-1000: 29 (1.3%), tests_pri_-950: 1.56
(0.1%), tes
ts_pri_-900: 1.40 (0.1%), tests_pri_0: 1251 (57.5%), check_spf: 0.13
(0.0%), che
ck_dkim_adsp: 5 (0.2%), check_bayes: 9 (0.4%), b_tokenize: 3.4 (0.2%),
b_tok_get
_all: 1.93 (0.1%), b_comp_prob: 2.0 (0.1%), b_tok_touch_all: 0.62
(0.0%), b_fini
sh: 0.13 (0.0%), check_razor2: 202 (9.3%), check_dcc: 838 (38.5%),
check_pyzor:
162 (7.4%), tests_pri_500: 5 (0.3%), get_report: 0.58 (0.0%)
Most of it (elapsed times) is produced by a call to:
$pms->get_tag('TIMING');
The CPU usage is obtained by calling Unix::Getrusage .
Mark
