Rick Macdougall wrote:
Any one have any idea what might cause an increase of scan times when
going from 3.3 to 3.3.1.
I've upgraded one server and the average scan time is now 4.3 seconds.
The 3 other servers still running 3.3 average 1.38
All running Centos on exactly the same hardware.
(I thought I sent a message on the same subject; looks like I forgot to
send it from the right account.)
I've seen something similar, however I'm seeing the difference from
3.2.5 to 3.3.x (both 3.3.0 and 3.3.1 show the same slowdown). Average
scan times have jumped from just under a second to just under four
seconds on the live mail stream, and about the same on a dev machine
with a small set of test messages. Different hardware and OS release
doesn't make much more than ~1% difference in scan times.
SA is installed via script, an initial configuration is set via script,
and a set of symlinks are used to manage which version is live. Another
script updates all of the rules channels we use (and if anything, that
should save a little CPU time because I dropped the SARE 90_2tld channel
for 3.3.x). Supporting Perl modules are all packaged (either Debian
stock, or local packages).
-kgd
