Guardian Digital Inc. >
InfoCenter >
Mailing List Archives >
Amavis
Amavis Mailing List Archive
Zitat von Max Clark <max@clarksys.com>:
> I've read in a few different places now that the recommended child processes
> is 2-3 per cpu on a system with quantities >10 detrimental to the overall
> system performance. With HT processors the system will identify 4 virtual
> processors on a 2 cpu system. Does this mean that my recommended child
> processes is 4-6 or 8-12? How do I go about benchmarking this properly to
> find the sweet spot?
The point is concurrency helps against latency, but only to the point you hit
another bottleneck.
So if you have many DNS based tests a high number of amavisd child is the way to
go (and a caching DNS server of course). If you have CPU intesive tasks like SA
concurrency will hurt you if the number is bigger then the number of processors
in your system or even earlier if you are on SMP. If your tests are all light
you hit the limit of your disk I/O if you do not go with ramdisk. This results
to the suggested 2-3 childs per CPU. Depending on your virus/spam tests you
should choose the upper or lower bound.
> On a dual 3.06GHz HT, 2GB Ram, Dual 15K RPM 36GB SCSI Disks system dedicated
> to amavisd-new w/ spamassassin and clamd running what should I use as
> starting points?
If you do many RBL lookups try a number from 6 - 8, if not 4 - 6. These are as
explained only starting points. Depending on your setup and surrounding YMMV.
Regards
Andreas
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
|
....