The aim is to help people avoid the catch-22 problem of not knowing how to properly size new installations of IMail.
The primary difficultly is breaking down usage among standard mail transfer, any scanning (if necessary), and web messaging (if necessary). Web messaging and virus scanning eat up resources.
1) What are the largest / larger known implementations of IMail?
There are quite a few that process 100,000+ E-mails/day, and some with as many as 100,000+ users. I don't know what configurations they are running, though.
2) What is the best way to conceptually measure the performance of various components of an IMail Server? Specifically what metrics determine the actual performance of a system and what factors should be considered for determining performance bottlenecks and threshholds (processor / network / memory / io utilization, user response time, SMTP delivery time, messages processed per minute / day, external user databases, etc.)
The key for mail transfer and scanning is the number of E-mails sent/received per day.
b) What type of information would you like to see on a best-practices performance guide?
"If CPU usage is high, use Task Manager, go to the "Processes" tab, and click on the "CPU" (not "CPU Time") button to sort the processes by the percentage of CPU time used. The processes towards the top of the list are using the most CPU time".
Although this is generic to any CPU usage issues, it's amazing how often people know that their CPU is at 100% but don't know to do the above.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches both viruses and vulnerabilities in E-mail, with no annual licensing fees.
--- [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/
