>The essential benefit of running a queue runner in this way is that you can
>run many. What tends to happen on IMail is that the active queue runners
>reduce down to just 1
?????
>30 processes (or whatever you set it to) is a maximum which only happens to
>incoming connections
the SMTPD server, then. I thought the 30 applied to SMTPD server +
SMTP- clients.
>use. Because IMail renames messages that are being processed it seems to be
>totally safe to be running multiple queue runners in this way as each just
>looks for messages which are not being processed. I have done this with
>1000's of messages during testing with no ill effects and a vast reduction
>in the time to clear the queue.
good to know, although I suppose if one/many of those msgs is a
kiler, will will still take out any queue runner that picks it up.
>You could even create a batch file which automatically runs 10 (for example)
>queue runners at these problem times.
"which reduces down to just one" ???
>Hope this helps clarify.
you're not done yet. :)) After such a batch of 10, are there 10 SMTP
processes in memory each sending msgs in parallel or "just one"?
btw, on that Imail/IMGate client that moves 150+ K msgs a day through
IMGate, the number of SMTP processes varies between 60 and
220. :))) At which point, on 256K manchine, I think he's memory
limited. I've recommended he up to 512. The CPU is averaging about
85 to 90% idle at all times.
Len
http://BIND8NT.MEIway.com: ISC BIND 8.2.2 p5 & 8.2.3 T6B for NT4 & W2K
http://IMGate.MEIway.com: Build free, hi-perf, anti-spam mail gateways
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
