Well, here, P4 HT 3.06 GHz, 2 GB RAM (just added 1GB, wanted to test
performance) Debian Sarge pretty standard, Perl 5.8.8 from Backports,
SA 3.2.0 from source, re2c 0.12.0 from source, a bunch of SARE and
openprotect rules, several plugins, sa-compile delivered this:
# time sa-compile
real 2m37.209s
user 2m17.220s
sys 0m14.943s
Plus, seems like SA isn't putting that much extra stress on my
servers, scantimes reported by Amavis are pretty much the same as
before the upgrade from 3.1.8 (from Debian backports), and top shows a
load index of 0.45-0.66 vs 0.22-0.33 before upgrading (Note: This
reports came from the 1 GB RAM setup). I guess the extra amount of
rules got compensated with the performance boost from sa-compile...
Luix
2007/5/10, Duane Hill <[EMAIL PROTECTED]>:
On Thu, 10 May 2007, Rosenbaum, Larry M. wrote:
>>
>> Took 10 mins on my 2.8gh 512mb ram, with a bunch of sares rules.
>>
>> You using .12.0 of re2c?
>
> Yes.
>
> I think most of the time is spent in the rule extraction steps and the
> gcc compiles, and not in the re2c steps. (gcc is v3.4.6)
>
>>> Yes, you are right, after "use warnings;". I ran SA3.2 on my site
> with
>>> "use bytes;" added, no problem so far. But it seems SA developers
> did
>> not
>>> mention this, they might have their reasons (break normalize_charset
> for
>>> one reason).
>>
>> Yes, exactly -- breaking one of the major 3.2.0 features is not a good
>> thing. :(
>
> Where can I find documentation on what normalize_charset does?
% perldoc Mail::SpamAssassin::Conf
...
normalize_charset ( 0 | 1) (default: 0)
Whether to detect character sets and normalize message content to
Unicode. Requires the Encode::Detect module, HTML::Parser version 3.46
or later, and Perl 5.8.5 or later.
--
-------------------------------------------------
GNU-GPL: "May The Source Be With You...
Linux Registered User #448382.
-------------------------------------------------
