Performance Issues

Ok... you guys helped me out a lot on the first question
today so I'm
going to pick your brain some more.  When I first started
with Maia, I
noticed that the postfix queue would build up quite fast,
with in one
night it could be as many and 2500 behind.  So after doing
some hunting
I found the bottle neck to be the SA Check at almost 10 - 15
seconds a
message at times.  Again, after picking over Google for 2
hours I found
that dcc, razor, pyzor and rbl were ALL turned on, so I
turned them all
off and my times went down to 2 - 8 seconds an email, which
will keep up
at least to where there may be 2-3 emails in the queue. 
However, this
doesn't seem to be the norm among SA users, my CPU averages
at 4% and
spikes constantly to 60-80% (2.4 GHz P4 - 1GB mem. 10
servers running).
I have moved my tmp dir for amavisd to a tmpfs file system
with no
avail.  Here is one of my TIMINGS: -

TIMING [total 9278 ms] - lookup_sql: 3 (0%), SMTP
pre-DATA-flush: 2
(0%), SMTP DATA: 77 (1%), body_hash: 1 (0%), maia_connect: 2
(0%),
maia_read_system_config: 1 (0%), maia_get_mysql_size_limit:
1 (0%),
lookup_sql: 3 (0%), mime_decode: 28 (0%), get-file-type3: 12
(0%),
decompose_part: 1 (0%), parts_decode: 0 (0%), lookup_sql: 6
(0%),
spam-wb-list: 1 (0%), SA msg read: 2 (0%), SA parse: 7 (0%),
SA check:
9024 (97%), update_cache: 2 (0%), maia_store_mail: 12 (0%),
deal_with_mail_size: 4 (0%), maia_record_tests: 44 (0%),
maia_set_mail_status: 4 (0%), fwd-connect: 8 (0%),
fwd-mail-from: 2
(0%), fwd-rcpt-to: 2 (0%), write-header: 4 (0%), fwd-data: 2
(0%),
fwd-data-end: 6 (0%), fwd-rundown: 2 (0%), main_log_entry:
13 (0%),
update_snmp: 1 (0%), maia_cleanup: 1 (0%), maia_disconnect:
0 (0%),
unlink-3-files: 1 (0%), rundown: 0 (0%)


You can see the SA Check is the culpret.  Is there anything
I can do to
log what SA does and get something like this so I can see
where the
bottle neck is?  Is there anything else I can do to speed up
SA?

Thanks a bunch,

Daniel


This email and any files transmitted with it are
confidential and intended for use only by the individual or
entity named above.  If you are not the intended recipient
or the employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified
that any disclosure, dissemination, distribution, copying of
this communication, or unauthorized use is strictly
prohibited.  Please notify us immediately by reply email and
then delete this message from your system.   Please note
that any views or opinions presented in this email are
solely those of the author and do not necessarily represent
those of Randolph County Government.  This email and any
file attachments have been scanned for potential viruses;
however, the recipient should check this email for the
presence of viruses and/or malicious code.  Randolph County
accepts no liability for any damage transmitted via this
email.
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

Shue, Daniel G. schrieb:
>
> You can see the SA Check is the culpret.  Is there
anything I can do to
> log what SA does and get something like this so I can
see where the
> bottle neck is?  Is there anything else I can do to
speed up SA?
>
>   
Daniel,

I strongly recommend to turn on network tests for a simple
reason: SA 
simply will catch lots more spam this way.
Naturally, wainting for all the test queries to return a
result takes 
time. SA (i.e. the MAil::SpamAssassin code) will not use
many resources 
in that time )apart from the loads of RAM every amavisd-maia
consumes).
I strongly suggest you invest into more RAM - get another 2
Gig and see 
how many amavisd-maia processes can be run simultaneously
without 
hitting swap.
Also you could set up a caching nameserver on localhost to
speed up the 
DNS lookups.

HTH

Dirk
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users