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.
In this case, I would suggest looking to see which IMail-related processes are using the most CPU time. If you can identify which process(es) are using the most CPU, it may be a bit easier to determine what would work best. For example, if it is the SMTP32.exe process, it might be possible to make a change in the way that it is called, so that it can only use one of the CPUs. Or, reducing the maximum number of processes further may help.
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.
There's always *something* that you can do. It's just a matter of the amount of effort involved to find it (and the cost of "it", if applicable, whether that be money or time) or versus the payoff. In this case, having an IMGate server in front of the IMail server may be an inexpensive way of reducing the CPU load on the IMail server, if you have a spare computer handy.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
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/
