"Alexis S. Panagides" <[EMAIL PROTECTED]> wrote:
>My basic question is how can I increase the throughput of my Qmail 1.03
>installation?
Easy: locate the bottleneck and remove it. :-)
>I have both concurrencylocal and concurrencyremote set to 120. But most of
>the time qmail has around 10 qmail-remote processes going.
If you only have 10 qmail-remotes running, but 2000+ queued remote
messages, something is seriously wrong. You need to open your sysadmin
toolkit and get under the hood. Are you CPU bound? Not likely. I/O
bound? Probably. N/W bound? Possibly? Run top, vmstat, iostat,
etc. until you can identify the critical resource.
>Every now and
>again I give it the ALRM signal and that shoots up the processes but then
>eventually things back down to the around 10 level.
Huh. From that, it sounds like you don't really have a problem. But
you said a test message took 2 hours, so something is definitely not
right. Did you trace your test message through the logs?
>A week or so ago I added the big-todo.patch although I am not really sure
>what it does. I didn't really see an improvement.
Oops. One shouldn't patch qmail, or any other system, for that matter,
unless one knows what the patch does.
>I have tcpserver at -c80 for qmail-smtpd.
Your problem is outgoing throughput, not incoming.
>One thing I find discouraging is when the queue inflates and a new email
>(my test email) gets sent in there is a delay. It is as if the queue really
>is a queue in the FIFO sense.
It *is* a queue. qmail-send can't do infinite work instantaneously. If
there's more work than it can handle, waiting jobs queue up.
Have you run qmailanalog?
-Dave
