Summary

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 133542578 for other detailed requirements.

Disk volumes

For medium and large configurations, separate disk volumes must be used for SQL databases (MDF), logs (LDF), and tempDB files, otherwise installations will take longer and performance will be affected.

SQL maximum server memory

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.

AI Powered Auto-curation

Please review AI Powered Auto-curation below for additional hardware requirements if you are using the feature to support inventory based applications such as AppClarity, Application Migration, and Patch Success.

ActiveEfficiency

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:

In this version of Tachyon there is no integration between ActiveEfficiency services and 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 25,000 seats


Small 1Small 2Medium 1
Maximum number of devices5005,00025,000

Tachyon Server and SQL Server

CPU cores21216
RAM10 GB32 GB48 GB
SQL Instance Max Memory2 GB10 GB20 GB
Number of Tachyon Switches111
Network interfaces (Tachyon)111
Disk space required for databases1 GB20 GB56 GB
ActiveEfficiency Server (Nomad) - see note above
CPU Coresincluded aboveincluded above1
RAM4 GB
Network interfaces (ActiveEfficiency)1

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


Medium 1Medium 2Large 1Large 2
Maximum number of devices25,00050,000100,000200,000
Tachyon Server
CPU Cores8121624
RAM24 GB36 GB58 GB94 GB
Number of Tachyon Switches1124
Network interfaces (outgoing to SQL plus incoming to Switches)2235
Remote SQL Server
CPU Cores48912
RAM12 GB32 GB44 GB60 GB
SQL Instance Max Memory8 GB28 GB40 GB56 GB
Disk space required for databases56 GB98 GB230 GB530 GB
ActiveEfficiency Server (Nomad) - see note above
CPU Cores1123
RAM4 GB4 GB4 GB8 GB
Network interfaces (incoming to ActiveEfficiency)1111

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 Medium environments (up to 50,000) and at least 10Gbps for Large environments (over 50,0000). For more detail please refer to Design Considerations: Network interfaces.

For larger or more complex configurations please contact 1E.

Tachyon Switch Server Sizing

The recommended configuration for a Tachyon Switch when hosted separately on its own server is 2 CPU Cores and 16 GB RAM.

AI Powered Auto-curation

Using the AI Powered Auto-curation feature you'll be able to increase the total amount of normalized software in your Inventory repositories. This is done using AI that integrates with the inventory consolidation process. By using AI your organization will benefit from significant numbers of normalized software and a reduced manual effort needed to normalize software.

Before starting, ensure you've met the Tachyon 5.0 - Requirements and completed the Tachyon 5.0 - Preparation steps.

The minimum total disk space required for the downloaded AI Package ZIP is approximately 12.5 GB at installation. This includes:

  • Binary and support files for AI and the directory structure is 8 GB
  • AIPackage ZIP file is 4 GB

While the downloaded AI Package is 5 GB, the unzipped contents are approximately 12.5 GB and are extracted to C:\ProgramData\1E\SLA Platform\AI\

Please note, the required disk space reduces to 8.2 GB after the first Catalog sync with the cloud. During the sync a check is made for any newer AI packages. If there is one, it's downloaded and a hash check of the ZIP file is made to make sure it's not corrupted. Once all checks are complete, the AI Package ZIP is deleted from C:\ProgramData\1E\SLA Platform\AI\ leaving an 8 GB disk space requirement.

1E Catalog 2.0 or later is required for the AI to work. 1E Catalog is included in the Tachyon Platform zip, and installed by Tachyon Setup.

Distinct Software Titles

Extra GB RAM for AI engine

1 to 5000

15

10000

17

20000

20

30000

24

40000

28

50000

33

60000

38

70000

43

80000

49

90000

55

100000

61

110000

67

120000

74

130000

82

140000

89

150000

97

160000

106

170000

114

If you're only using a System Center Configuration Manager (SCCM) connector then use the SCCM database as a guide for how much extra RAM you need before installation. We recommend using the SLA-Data database query after installation to double-check memory requirements. However, additional RAM will be required if you're going to use a Tachyon connector (for Inventory or Patch Success) either on its own, or with other connectors including SCCM. In this case, use the SLA-Data database query after installation and when the connectors are collecting data.

Physical memory for AI Powered Auto-curation is calculated on the basis of the number of records the AI has to process. Use the accompanying table as a quick reference for the memory requirements needed by the AI.

For virtual machines, the AI Engine action will not work if you're using a dynamic memory configuration. You'll need to allocate dedicated memory.

You can also run the following query on your SCCM database to calculate your memory requirements. This is primarily aimed at people who have not already installed Tachyon and want to estimate the required RAM:

SCCM database query
/*SCCM database query to get number of distinct software titles from SCCM database*/
USE [YourSCCMDBName]
GO
SELECT COUNT(*) AS 'Distinct Software Titles'
FROM (
	SELECT DISTINCT DisplayName0 AS Title FROM [v_ADD_REMOVE_PROGRAMS] WITH (NOLOCK)
	UNION
	SELECT DISTINCT [Caption0] AS Title FROM [v_GS_OPERATING_SYSTEM] WITH (NOLOCK)
) AS Titles

Run this query on SLA-Data if you already have Tachyon installed and are considering enabling AI:

SLA-Data database query
/*SLA query to get number of distinct software titles from SLA-Data database*/
USE [SLA-Data]
CREATE TABLE #Software
       (
              [SoftwareID]                      INT IDENTITY(1,1) PRIMARY KEY,
              [DataSource]                      NVARCHAR(255) COLLATE DATABASE_DEFAULT,
              [SoftwareIdent]                   NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [SoftwareIdent_Hash]		        VARBINARY(128),
              [Vendor]                          NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [Vendor_Hash]			            VARBINARY(128),
              [Title]                           NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [Title_Hash]                      VARBINARY(128),
              [Version]                         NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [Version_Hash]                    VARBINARY(128),
              [ColloquialVersion]               NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [ColloquialVersion_Hash]          VARBINARY(128),
              [Edition]                         NVARCHAR(MAX) COLLATE DATABASE_DEFAULT,
              [Edition_Hash]                    VARBINARY(128),
              [NormalizedProductID]             INT
       );
SELECT * FROM #Software
EXEC [usp_ReportDataEx_se] 1, N'Software', N'#Software';
  
SELECT count(*) AS 'Distinct Software Titles'
FROM
(
SELECT DISTINCT [Title] FROM #Software
) a

DROP TABLE #Software