From: "Robert - elists" <[EMAIL PROTECTED]>
Sent: Friday, 2008, January 18 21:14
You can't run the rules in score-order without driving SA's performance
into the ground.
The key here is SA doesn't run tests sequentially, it runs them in
parallel as it works its way through the body. this allows for good,
efficient use of memory cache.
By running rules in score-order, you break this, forcing SA to run
through the body multiple times, degrading performance.
Mr K
SA is an awesome, incredible product and tool.
Wonderful Job!
I am not an expert on the programming theory, design, and implementation
behind SA.
So... are you saying SA takes a single email and breaks it apart into
several pieces and scans those pieces via multiple processing threads and
comes back with an additive single end result for that single emails
multiple scan processing threads?
Before going further you should try to find a really good discussion of
how perl parses regular expressions. Oversimplifications can lead to
massive pessimization of the code in the name of optimization.
{^_^}
