Contents
Sizing and deployment considerations
For optimum performance, we recommend the following:
| Single-server deployment | Distributed server deployment | ||||||
|---|---|---|---|---|---|---|---|
|
| ||||||
| Number of machines | 5,000 | 25,000 | 50,000 | 50,000 | 100,000 | 200,000 | 500,000 |
| Benchmark configuration | |||||||
| Maximum downloads per hour | 5,000 | 12,500 | 25,000 | 25,000 | 50,000 | 100,000 | 250,000 |
| ActiveEfficiency server (total including SQL Server) | ActiveEfficiency Server (total) | ||||||
| CPU cores | 2 | 2 | 3 | 1 | 2 | 3 | 6 |
| RAM | 4 GB | 6 GB | 8 GB | 4 GB | 4 GB | 4 GB | 4 GB |
| ActiveEfficiency Server service | |||||||
| CPU cores | 1 | 1 | 1 | 1 | 2 | 3 | 6 |
| RAM | 4 GB | 4 GB | 4 GB | 4 GB | 4 GB | 4 GB | 4 GB |
| ActiveEfficiency Scout (n/a) | |||||||
| ActiveEfficiency database | Database Server (total) | ||||||
| CPU cores | 1 | 1 | 2 | 2 | 2 | 3 | 6 |
| RAM | 2 GB | 4 GB | 6 GB | 8 GB | 8 GB | 10 GB | |
| SQL Server instance max memory | 1 GB | 2 GB | 3 GB | 3 GB | 4 GB | 4 GB | 6 GB |
| Disk space required for database | 4.5 GB | 4.5 GB | 4.5 GB | 4.5 GB | 5 GB | 6 GB | 9 GB |
| SQL Server HDD requirements | |||||||
| ActiveEfficiency database MDF | 4 GB | 4 GB | 4 GB | 4 GB | 4 GB | 4 GB | 8 GB |
| ActiveEfficiency database LDF | 50 MB | 50 MB | 50 MB | 50 MB | 250 MB | 500 MB | 1 GB |
| TempDB MDF | 50 MB | 100 MB | 200 MB | 200 MB | 400 MB | 1 GB | 1.5 GB |
| TempDB LDF | 4 MB | 8 MB | 16 MB | 16 MB | 32 MB | 64 MB | 100 MB |
Benchmarking criteria
- Benchmarked against Windows Server 2012 R2 Hyper-V infrastructure, with database and application server components on separate virtual machines
- CPU – Hyper-V host CPU configuration: 2x Intel Xeon CPU E5-2407 v2 @ 2.40GHz, 10M Cache, 4C, Max Mem 1333MHz
- Networking – virtual machines connected over a 1Gbps link through a 1Gbps physical switch
- Database storage – Samsung 850 EVO solid state drives (SSDs) attached locally to the Hyper-V host with up to 98k/90k IOPS (4K random read/write QD32), and MDF, LDF and TempDB on separate SSDs
Recommendations
- Servers can be deployed either on physical or virtual machines. For deployment on a virtual machine, assign the CPU cores at 100% virtual machine reserve
- Database Server:
- deploy data, logs and TempDB on separate physical disks
- configure SQL Server with maximum server memory limit and not at the defaults to consume unlimited memory
- for sizing the Database server in the recommendations above, up to 4GB RAM has been added for the operating system on top of SQL Server instance RAM requirements.