Server sizing guidelines and recommended configurations for on-premises installation in customer environments.

On-premises configurations

The tables below are minimum specifications for on-premises installations. Tachyon is recommended to be installed on a dedicated server, and can be installed on physical or virtual hardware. 

A Tachyon system comprises a single Master Stack and one or more Response Stacks. The tables and diagrams show details for a single server which combines Tachyon Master and Response Stacks with either local or remote SQL Servers. Use the same specifications for separated Master and Response Stack servers.

Each Response Stack can have up to five Tachyon Switches and one Background Channel. Each Switch can support up to 50,000 devices therefore a single server with 5 Switches and one Background Channel can support up to 250,000 devices.

Best performance is achieved using a local SQL Server installation but you can install Tachyon and SQL Server on separate (split) servers. A separate SQL Server is required if it is to be shared with other customer applications, and its CPU and RAM should be increased accordingly. Please refer to SQL Server requirements for other detailed requirements.

For medium and large configurations, separate disk volumes are required for SQL databases, logs, and tempDB. When Tachyon and SQL Server are installed on the same server, then the SQL Server setting maximum server memory must be set to match the value in the table.

The tables below include ActiveEfficiency Server to support Nomad features only. ActiveEfficiency can be installed on the Tachyon server for small systems. Medium and large systems (over 50000) require separation of incoming network traffic from Nomad and Tachyon clients. Therefore, either ActiveEfficiency or the Response Stack is installed on a separate server, or if both are installed on the same server there are additional networking and DNS requirements, as described in Design Considerations: ActiveEfficiency Server.

For guidance on installing ActiveEfficiency on a separate web server, please refer to ActiveEfficiency Server 1.10 - Implementation.

Additional hardware is required when using ActiveEfficiency Server to support AppClarity 5.2 or Shopping, which require an ActiveEfficiency Scout, please refer to:

AppClarity 5.2 and Shopping 5.6 use ActiveEfficiency Scout to get data from Configuration Manager. This version of ActiveEfficiency does not get data via Tachyon or SLA.

CPU cores listed in the tables below are logical cores (physical or virtual). For deployment on a virtual machine, the CPU cores should be assigned at 100% virtual machine reserve.

On this page:

Combined Tachyon and SQL Server - up to 5,000 seats

Small 1Small 2
Maximum number of devices5005,000

Tachyon Server and SQL Server

CPU cores212
SQL Instance Max Memory2 GB10 GB
Number of Tachyon Switches11
Network interfaces (Tachyon)11
Disk space required for databases1 GB60 GB
30 GB
20 GB
ActiveEfficiency Server (Nomad) - see note above
CPU Coresincluded aboveincluded above
Network interfaces (ActiveEfficiency)

Separate Tachyon and SQL Server - up to 500,000 seats

Medium 1Medium 2Large 1Large 2Large 3
Maximum number of devices25,00050,000100,000200,000500,000
Tachyon Server
CPU Cores812162448
RAM24 GB36 GB48 GB56 GB128 GB
Number of Tachyon Switches112410
Network interfaces (incoming to Switches plus outgoing to SQL Server)223511
Remote SQL Server
CPU Cores68121632
RAM16 GB24 GB32 GB48 GB96 GB
Disk space required for Database200 GB400 GB800 GB1,600 GB4,000 GB
Logs100 GB200 GB300 GB600 GB1,400 GB
TempDB100 GB150 GB200 GB400 GB800 GB
ActiveEfficiency Server (Nomad) - see note above
CPU Coresincluded aboveincluded aboveincluded aboveincluded above
please refer to Nomad,

Network interfaces (incoming to ActiveEfficiency)

A server hosting a Tachyon Response Stack requires a dedicated network interface (MAC Address and IP Address) for each Switch, and for the connection to the remote SQL Server instance used for the Responses database to keep incoming traffic from clients separate from the outgoing traffic to the Response database. This dedicated SQL connection must be at least 1Gbps for environments (up to 50,000) and at least 10Gbps for environments (over 50,000). For more detail please refer to Design Considerations: Network interfaces.

For larger or more complex configurations please contact 1E.