Table of Contents

Server Scalability and Sizing


This document is intended to help define the server environments required to host various sizes of Xcalibur W installations. The recommendations below should be considered starting points. As you gain experience administering the Xcalibur W system, the requirements should be modified to suit your organization's needs.

1,000 Devices or Less


All Management Suite Services Hosted on One Server

1,000 to 2,000 Devices


All Management Suite Services Hosted on One Server

2,000 to 6,000 Devices


Management Suite Services Hosted on Separate Servers

Server 1 – IIS Server

Server 2 - Database Server

6,000 to 10,000 Devices


Core and Database on Separate Servers

Server 1 – IIS Server

Server 2 - Database Server

10,000 to 20,000 Devices


Core and Database on Separate Servers

Server 1 – IIS Server

Server 2 - Database Server

20,000+ Devices


Core and Database on Separate Servers

For Xcalibur W installations of this size, we recommend obtaining further tuning assistance from XcaliburW Professional Services or one of our Valued Expert Solutions Providers.

Pulse Delay


The pulse value (in seconds) provided in each section above assumes the maximum number of devices in the range (i.e. 20,000 devices in the 10,000 to 20,000 Devices section). The ratio of the pulse delay to the number of devices ([Pulse delay in seconds] / [number of devices]) should not exceed 0.15.

Note on Database


Microsoft SQL Server 2012 Express has a 10GB database size limitation. If the limit is reached, the server will stop functioning properly and the database will no longer function correctly. Each instance of Xcalibur W Agent may use 1MB or more during its lifecycle. If using SQL Server 2012 Express, carefully monitor disk usage and upgrade to SQL Server 2012 before reaching the 10GB limit.

Although Xcalibur W supports MySQL, experience and testing have shown that Microsoft SQL Server behaves and performs far better when dealing with 2,000+ devices.