> I'm not aware of a way to do this with services, but if there > is a way, I'm > sure someone will respond. However, my first question would > be whether CPU > resources are an issue here -- are you really at or close to 100% CPU > usage? Normally, with SQL, the resource hog is memory. > Splitting up the > processors will mean that if IMail or SQL is at 100% CPU > usage, the rest of > the CPU usage will go unused, which would be more likely to > hurt than help.
Absolutely true. What I was pondering was, we really want to place a priority on keeping SQL Server up and running, and let iMail churn away on its one CPU. The only time we ever have problems is when someone sends a bunch of mail from one of our web servers... other than that, the two applications actually do still co-exist quite well. So my thought is, when 'things get busy', the priority is to keep the database server running well, and let iMail slowly work its way through the queue. Memory has been tuned in such a way as to allow SQL Server "up to" 512MB RAM (sometimes it takes a little more than it should, but overall it has been behaving), and the rest of RAM is dedicated to iMail/mxGuard/ClamAV. We are configured right now to run 20 iMail SMTP processes and 10 mxGuard processes, to keep iMail's memory usage in check -- which has actually been more of an issue, especially during bulk mailings when we experienced a great many smtp-related processes spawned at once. I'm totally ready to hear that there's not much else we can do... but open to any additional tweaks including processor isolation between the two apps. Thanks for responding!! Marc To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
