You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Robert Schetterer <rs...@sys4.de> on 2015/05/03 08:40:03 UTC
need_tags
Hi , i try to understand
this
http://search.cpan.org/dist/Mail-SpamAssassin/lib/Mail/SpamAssassin.pm
need_tags
...
Currently the only tag that needs to be explicitly requested is 'TIMING'
...
the goal would be to have time stats of every rule matching in logs,
without
advanced debug levels on production servers for better analysis
Any Idea ?
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
Re: need_tags
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 5/4/2015 7:42 PM, Mark Martinec wrote:
>>> 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 .
Neat. I'll talk it over with Joe tomorrow.
Re: need_tags
Posted by Mark Martinec <Ma...@ijs.si>.
>> 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
Re: need_tags
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 5/4/2015 7:14 PM, Mark Martinec wrote:
>
> On 2015-05-04 15:42, Kevin A. McGrail wrote:
>> I believe this setting is solely for profiling of spamassassin. See
>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5356 but I doubt it's
>> of much use to the general public.
>
> 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.
Neat. Can you cut and paste an example log and perhaps we can mimic it
in spamd easily?
regards,
KAM
Re: need_tags
Posted by Mark Martinec <Ma...@ijs.si>.
> On 5/3/2015 2:40 AM, Robert Schetterer wrote:
>> Hi , i try to understand
>> this
>>
>> http://search.cpan.org/dist/Mail-SpamAssassin/lib/Mail/SpamAssassin.pm
>>
>> need_tags
>> ...
>> Currently the only tag that needs to be explicitly requested is 'TIMING'
>> ...
>>
>> the goal would be to have time stats of every rule matching in logs,
>> without
>> advanced debug levels on production servers for better analysis
On 2015-05-04 15:42, Kevin A. McGrail wrote:
> I believe this setting is solely for profiling of spamassassin. See
> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5356 but I doubt it's
> of much use to the general public.
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.
Mark
Re: need_tags
Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
On 5/3/2015 2:40 AM, Robert Schetterer wrote:
> Hi , i try to understand
> this
>
> http://search.cpan.org/dist/Mail-SpamAssassin/lib/Mail/SpamAssassin.pm
>
> need_tags
>
> ...
> Currently the only tag that needs to be explicitly requested is 'TIMING'
> ...
>
> the goal would be to have time stats of every rule matching in logs,
> without
> advanced debug levels on production servers for better analysis
I believe this setting is solely for profiling of spamassassin. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5356 but I doubt it's
of much use to the general public.
regards,
KAM