Bug 5284 - MIME_BOUND_NEXTPART has bad performance
Summary: MIME_BOUND_NEXTPART has bad performance
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 normal
Target Milestone: 3.2.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard: close before perceptron
Keywords:
Depends on:
Blocks: 5270
  Show dependency tree
 
Reported: 2007-01-08 15:12 UTC by Theo Van Dinter
Modified: 2007-01-09 23:26 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Theo Van Dinter 2007-01-08 15:12:39 UTC 
In the 3.1 score gen mass-check run, this rule didn't do terribly, but also
wasn't great.  At this point, the rule is basically useless (from last night's
mass-check run):

  0.452   0.4522   0.4530    0.500   0.50    0.00  MIME_BOUND_NEXTPART

So we either need to do some more work and fix this, or just drop the rule.
Comment 1 Justin Mason 2007-01-09 01:46:38 UTC 
wow, how did that not get removed during the big rule pruning?
I vote for dropping it.
Comment 2 Justin Mason 2007-01-09 02:48:31 UTC 
we don't need to resolve this before mass-checks, actually; if needs be, we can
remove the rule just before running the perceptron (and just ignore the hits in
the logs).  updating status accordingly
Comment 3 Theo Van Dinter 2007-01-09 23:26:13 UTC 
ok, the performance went down since the last time I checked:

 27.865  31.7711   3.2772    0.906   0.59    0.00  __NEXTPART_NORMAL
 28.172  32.0449   3.7978    0.894   0.58    0.00  __NEXTPART_ALL
  0.308   0.2737   0.5206    0.345   0.45    0.00  MIME_BOUND_NEXTPART

so yeah, it's gone.