2.1.5 Sizing guide
The following information can be used as a guideline when deploying MataDefender Email Gateway Security in your organization. Since there are many factors that may affect performance, these test results should not be viewed as performance guarantees.
Factors that may affect performance
-
Package and configuration
-
set of engines (which and how many)
-
configuration (e.g. CDR is enabled)
-
-
System environment
-
profile (CPU, RAM, Storage)
-
-
Traffic characteristics
-
average attachment number/size/type
-
Test results
Performance is measured by the number of processed emails in one hour interval. In the test scenarios below, the traffic was generated by using real-world attachment number/attachment size/attachment type distributions. In all cases, MetaDefender Email Gateway Security was deployed as an SMTP Proxy. For test cases with CDR enabled, CDR was allowed for all possible file types.
Results
CPU cores |
Memory (GB) |
OS |
Engine package |
Duration |
Processed emails |
4 @2.1 GHz |
16 |
Windows Server 2016 |
4 engine package + Data sanitization + DLP + Yara |
1h |
6 000 |
8 @2.1 GHz |
16 |
Windows Server 2016 |
4 engine package + Data sanitization + DLP + Yara |
1h |
8 000 |
16 @2.1 GHz |
16 |
Windows Server 2016 |
4 engine package + Data sanitization + DLP + Yara |
1h |
8 000 |
8 @2.1 GHz |
16 |
Windows Server 2016 |
4 engine package + Data sanitization + DLP + Yara |
1h |
9 000 |
16 @2.1 GHz |
16 |
Windows Server 2016 |
4 engine package + Data sanitization + DLP + Yara |
1h |
11 500 |
8 @2.1 GHz |
16 |
Windows Server 2016 |
8 engine package + Data sanitization + DLP + Yara |
1h |
6 500 |
16 @2.1 GHz |
16 |
Windows Server 2016 |
8 engine package + Data sanitization + DLP + Yara |
1h |
8 000 |
8 @2.1 GHz |
16 |
Windows Server 2016 |
8 engine package + Data sanitization + DLP + Yara |
1h |
7 500 |
16 @2.1 GHz |
16 |
Windows Server 2016 |
8 engine package + Data sanitization + DLP + Yara |
1h |
12 000 |
On-site Exchange deployment
In case of on-site Exchange deployment scenarios the resource needs of the Microsoft Exchange Server must also be taken into consideration.