http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5354
------- Additional Comments From [EMAIL PROTECTED] 2007-03-11 19:55 -------
up'ing to sa-trunk/r516950
build as usual.
then,
date > compile_time.txt
/usr/local/spamassassin/bin/sa-compile --sudo -D
date >> compile_time.txt
note the new progress display. helpful, thanks.
on an 800MHz G4, the compile now completes without error !! and,
cat compile_time.txt
reports,
Sun Mar 11 19:10:19 PDT 2007
Sun Mar 11 19:41:10 PDT 2007
i.e., an ~ 31 minute compile time.
now, a few question(s):
(1) how do we verify that the compiled rules are working, and how 2 _measure_
the improved (hopefully) performance?
if we ARE using sa-compile,
(2) do compiled rules automatically take precedence over uncompiled rules? or,
must we remove the uncompiled rules from the rule path?
(3) should (must?) we run sa-compile at every rule update? e.g., if we're
sa-update'ing once/hr, running sa-compile hourly is a bit cpu intensive.
(4) does sa-compile somehow detect changes and only compile those? or does it
recompile ALL available rules each time?
thanks.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
