Single-server deploymentDistributed deployment


Number of machines5,00025,00050,000100,000200,000500,000
Benchmark configuration
Number of machines5,33717,72647,57485,417172,412427,263
Number of applications19,30026,00031,70022,50049,00077,000
Number of installations395,0001.1M3.2M5.2M9.1M31.4M
Combined Application server (AppClarity, ActiveEfficiency)
CPU cores4




RAM4 GB




ActiveEfficiency server (total)
CPU cores344668
RAM3 GB8 GB8 GB12 GB20 GB40 GB
ActiveEfficiency Scout application
CPU cores 1 2 2 2 2 4
RAM 1 GB 4 GB 4 GB 8 GB 16 GB 32 GB
ActiveEfficiency Server service
CPU cores 1 2 2 4 4 4
RAM 1 GB 4 GB 4 GB 4 GB 4 GB 8 GB
AppClarity server (including Catalog)
CPU cores122244
RAM1 GB4 GB4 GB8 GB16 GB32 GB
Database server (total)
CPU cores2446610
RAM12 GB12 GB20 GB36 GB60 GB96 GB
SQL Server instance maximum memory8 GB8 GB16 GB32 GB56 GB88 GB
Disk space for database12.5 GB18 GB32 GB55 GB105 GB267 GB
SQL Server HDD requirements
ActiveEfficiency database MDF4 GB4 GB8 GB16 GB32 GB72 GB
ActiveEfficiency database LDF50 MB50 MB50 MB50 MB100 MB200 MB
AppClarity database MDF2 GB6 GB14 GB24 GB48 GB128 GB
AppClarity database LDF1 GB2 GB4 GB8 GB16 GB48 GB
1E Catalog database MDF2 GB2 GB2 GB2 GB2 GB2 GB
1E Catalog database LDF2 GB2 GB2 GB2 GB2 GB2 GB
TempDB MDF1 GB1 GB1 GB2 GB3 GB12 GB
TempDB LDF64 MB100 MB200 MB400 MB1 GB2 GB
Expected Configuration Manager TempDB growth1 GB1 GB2 GB2 GB4 GB28 GB
End-to-end synchronization time (approximate)15 mins1 hr2 hrs3 hrs6 hrs23.5 hrs


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
  • For environments with 25,000 or more computers, if the network usage between ActiveEfficiency, AppClarity and Database servers is a concern during the synchronization process, have a dedicated 1Gbps connection between these servers for the synchronization traffic
  • 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
  • AppClarity Server:
    • For environments with 200,000 or more computers, update the following entry for AppClarity in the  AMP.Coordinator.ServiceHost.config  xml file:
        <add key="ActiveEfficiencyWebServiceTimeOutSecs" value="600"/>
      This setting increases the web service response timeout duration to accommodate the long response time for a particularly large web service request during the AppClarity sync.