With the addition of Bayesian statistical filtering the computational needs were substantially increased as compared to the previous Praetor v1.5. For each message, hundreds of tokens may be present that require as many token database accesses to obtain the good and bad counts from past training. Thus, there are an estimated 10 times more floating point operations to compute the overall statistical probability that the message under review is spam, a value we call spamicity.
The following are CMS's recommendations for optimal performance of a Praetor G2 installation. (Praetor will still function with a lesser machine but delivery may be slowed down a few seconds.) These recommendations are based upon the number of email users and assume an average of 50 received messages per person per day, including spam.
|
Site size (users) |
Rcvd emails per day |
CPU |
Speed |
RAM |
Free Disk Storage |
Windows |
Database Server |
|
10 - 49 |
< 2,500 |
Pentium IV |
1.5 GHz |
512 MB |
10 GB |
Pro edition |
MSDE |
|
50 - 99 |
< 5,000 |
Pentium IV |
2.0 GHz |
1 GB |
15 GB |
Server edition |
MSDE |
|
100 - 249 |
< 12,500 |
Pentium IV |
2.6 GHz |
1 GB |
20 GB |
Server edition |
MSDE |
|
250 - 999 |
< 50,000 |
Pentium IV |
> 3 GHz |
1 GB |
40 GB |
Server edition |
SQL Server |
|
1,000 - 4.999 |
> 50,000 |
Multiple Pentium IV or Xeon |
> 3 GHz |
2 GB |
200 GB |
Server edition |
SQL Server |
|
> 5000 |
> 250,000 |
Multiple Pentium IV or Xeon in a cluster |
> 3 GHz |
2 GB |
Clustered disk array |
Server edition |
Separate SQL Server |
Use the above as guidelines focusing on the volume of email received each day. CMS realizes that your company may have different needs that require different configurations. To further discuss how to fit Praetor.G2 into your email system, please contact CMS Support
If you are trying to decide whether to install Praetor on a stand-alone machine or onto the same machine as your Windows 200x-based mail server, click here.
Keep in mind that Microsoft has put limits as follows:
Non-server versions of the Windows OS can only have 10 simultaneous IP sessions
MSDE can only have 8 concurrent accesses before a "workload governor" is activated to artificially delay each access by several milliseconds. Also, there is a 2GB database (MDF) file limit