On Tue, 2 Dec 2003 10:38:45 -0500 (EST)
Ed Phillips <[EMAIL PROTECTED]> wrote:
> Also, from another glance at the source, it appears that clamd will go
> into a "buzz-loop" waiting for a free thread slot if there are already
> MaxThreads threads active. Not the best solution for the "busiest"
> s
On Tue, 2 Dec 2003, Ken McKittrick wrote:
> Ed
>
> Amavisd-new and Clamd are the bottleneck on this system. With 8 amavisd
> processes, clamd runs with 5 threads. That goes up to 6 threads with 12
> amavisd processes. This might be the most I can get on an 8 cpu system.
We use MIMEDefang + clamd
Ed
Amavisd-new and Clamd are the bottleneck on this system. With 8 amavisd
processes, clamd runs with 5 threads. That goes up to 6 threads with 12
amavisd processes. This might be the most I can get on an 8 cpu system.
I'm still fine tuning this machine for maximal throughput.
Thanks
Ken McKit
On Tue, 2 Dec 2003, Ed Phillips wrote:
> On Tue, 2 Dec 2003, Ken McKittrick wrote:
>
> > Hello
> >
> > I have Postfix 2.0.16, Amavisd-new, SpamAssassin, and Clamav 0.65
> > running on a Enterprise 4500 with 8 CPU's. It's configured to use 16
> > Amavisd processess and the Clamav.conf has MaxThread
On Tue, 2 Dec 2003, Ken McKittrick wrote:
> Hello
>
> I have Postfix 2.0.16, Amavisd-new, SpamAssassin, and Clamav 0.65
> running on a Enterprise 4500 with 8 CPU's. It's configured to use 16
> Amavisd processess and the Clamav.conf has MaxThreads set to 40. I only
> see 6 clamd threads. I don't th
Hello
I have Postfix 2.0.16, Amavisd-new, SpamAssassin, and Clamav 0.65
running on a Enterprise 4500 with 8 CPU's. It's configured to use 16
Amavisd processess and the Clamav.conf has MaxThreads set to 40. I only
see 6 clamd threads. I don't think that Clamd is keeping up with
Amavisd.
Any id
