What follows are a some tricks I learned quite some time ago
and which helped me to fine-tune ASSP performance on win32
platform
* Increase clamd priority: sometimes clamD may slowdown the
mail processing since it will ask for CPU cycles to scan an
incoming message and may start fighting with ASSP and/or
other applications runningon the system; to solve this issue
download the process explorer tool from this page
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
and just extract the files from the zip to whatever suitable folder,
then run the procexp.exe program, locate the "clamd" process,
right click it and change its priority to "above normal" (warning
DO NOT go over that and do NOT change other priorities) so
that ClamD will get a priority boost just when needed and will be
able to complete the scans in a snap
* Disable the indexing of ASSP folder (and subfolders): the indexing
service in windows may be useful some times, but if you are running
in on the ASSP box and you don't need it, either stop and disable the
service, or ensure that the ASSP folder and subfolder are *excluded*
from the indexing, otherwise, each and every file ASSP will write on
disk, including spam, notspam, the logs and so on will cause the
index
server to kick in an start parsing and indexing the file.. eating CPU
* Disable realtime AV scanning for the ASSP folder: if the box on which
you're running ASSP is also running an antivirus with a "realtime"
scan
ensure to *exclude* the ASSP folder (and subfolders) from such a scan
otherwise it may cause conflicts and, in general it will slowdown
ASSP
operations (remember, ASSP does a lot of disk I/O)
* Fine tune your disk subsystem: ASSP perform a lot of disk I/O, so
ensure
to keep your disks in good shape, defragment it, and if the disks are
slow
consider buying faster disks; a decent amount of memory and fast disks
will considerably speed up your ASSP
* Keep your logs small: not exactly a big improvement, and it will
generate
a number of logfiles, but setting the log rotation to one day, will
help speeding
up log searches since the logfile size will be smaller; also, if you
need to run
frequent log searches, consider using "grep" from command line instead
of
using the ASSP built in search.. what ? You don't have "grep" on
windows ?
Well, pick this http://sourceforge.net/projects/unxutils add the "bin"
and the
"usr\local\wbin" paths to your PATH environment variable and you'll
have
quite a number of *nix commands available at your fingertips
* Avoid using too many DNSBLs/URIBLs: keep in mind that many RBLs are
somewhat "overlapped" so, avoid using a high number of lists and just
use
the most efficient ones, if in doubt, add the "testing" lists, let
them run for a
while, then look at the maillog and check how many hits those RBLs had
and then decide yourself if the tradeoff of performing an additional
lookup
is worth or if it would be better throwing away a given RBL
HTH
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
