You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by Apache Wiki <wi...@apache.org> on 2005/07/24 10:24:21 UTC

[Spamassassin Wiki] Update of "RulesProjMoreInput" by LOAFER

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by LOAFER:
http://wiki.apache.org/spamassassin/RulesProjMoreInput

The comment on the change is:
Adding a few suggestions.

------------------------------------------------------------------------------
    * checked rules and their results are kept in a version-control history, so benefits of VC are available
    * ongoing visibility of hit-rates of the existing ruleset, against fresh corpora
  
+ (LOAFER: Suggestion: It would be good to know the % runtime figure for a sandbox rule as a missing boundary can take a rule from 1.5% to 0.0n% performance hit easily
+ {{{
+  perl -d:DProf mass-check -j=1 spam:dir:some_reasonable_sample_set_including_hits_and_misses
+  dprofpp -O 2000 > perf.log
+ }}}
+ Someway of scheduling a small run during the development day would be useful, rather than waiting for the nightly.
+ An email of users completed results would be nice to see too.
+ )
+ 
  (TODO: migrate the ruleqa CGI onto the SpamAssassin zone so this is still visible, even though the automc stuff is disabled)
  
  === List-Driven Mass-Checks ===
@@ -71, +80 @@

  rules may depend on other rules that were not changed as part of the same
  commit. So I think the "email with attached rules file" is still a better
  model.'
+ LOAFER: There are eval rules to consider too.