Other versions

Reference: Host system sizing guidelines

You can use this reference to estimate host system requirements for Tanium™ Core Platform component servers. Exact requirements vary according to dynamic usage behavior, including, but not limited to:

  • The number of Windows, Mac, Linux, and UNIX devices being managed
  • The number of saved questions that are configured to automatically archive results
  • Whether the archived results for a given question are being aggregated rather than stored as individual rows within the database.
  • The number of configuration, state, or property data elements that need to be stored from each computer per saved question
  • The size of each data element being archived from managed computers
  • The number of potential unique values computers might return for any given data element
  • The frequency at which the data elements are to be archived over time
  • The Tanium solutions you intend to use in addition to the Core Platform.

Because the usage behavior is so different among customers, the requirements presented in the following tables are based on representative data from a large number of deployments ranging in size from less than 1,000 to more than 400,000 managed devices.

Tanium Server host system

Use the following tables to estimate Tanium Server host system specifications. The columns indicate the total endpoints deployed. In an HA deployment, each Tanium Server in the cluster must meet or exceed the requirements for the total number of endpoints targeted by your deployment. (Each must be able to independently handle load from the full deployment in the event of failure.)

Table 1:    Tanium Server operating system sizing
Edition Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Microsoft Windows Server 2008 R2 SP1 or later
Standard    
Enterprise
Data Center
Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Standard
Enterprise

 

Table 2:   Tanium Server hardware sizing
Edition Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Server Device Physical or virtual Physical or virtual Physical or virtual Physical¹ Physical¹ Physical¹
CPU Core² 4 8 16 24 40 80
Memory 16 GB 32 GB 48 GB 96 GB 256 GB 512 GB
Disk Space³ 100 GB 250 GB 400 GB 750 GB 1.5 TB 3 TB
¹ Tanium strongly recommends the host system have 10Gb network cards with chipsets from Intel for deployments over 70,000 endpoints.
² Calculate CPU cores based on only the physical cores from allocated CPUs—not the logical cores available with Hyper-Threading enabled.
³ Total space for Microsoft OS and Tanium Server.

 

Tanium Module Server host system

Use the following tables to estimate Tanium Module Server host system specifications. The columns indicate the total endpoints deployed.

Table 3:   Tanium Module Server operating system sizing
Edition Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Microsoft Windows Server 2008 R2 SP1 or later
Standard
Enterprise
Data Center
Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Standard
Enterprise

Table 4:   Tanium Module Server hardware sizing
Edition Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Server Device Physical or virtual Physical or virtual Physical or virtual Physical or virtual
CPU Core 4 8 12 16
Memory 8 GB 16 GB 24 GB 48 GB
Disk Space 150 GB 150 GB 200 GB 300 GB

Tanium Zone Server host system

Use the following tables to estimate Zone Server host system specifications. The columns indicate the number endpoints reporting through the Zone Server. In a Zone Server HA deployment, each Zone Server must be provisioned to independently handle load for the cluster in the event one of the nodes fails.

Table 5:   Tanium Zone Server operating system sizing
Edition Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Microsoft Windows Server 2008 R2 SP1 or later
Standard
Enterprise
Data Center
Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Standard
Enterprise

Table 6:   Tanium Zone Server hardware sizing
Edition Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Server Device Physical or virtual Physical or virtual Physical or virtual Physical¹ Physical¹ Physical¹
CPU Core² 4 8 16 24 40 80
Memory 8 GB 16 GB 24 GB 48 GB 128 GB 256 GB
Disk Space³ 100 GB 250 GB 400 GB 750 GB 1.5 TB 3 TB
¹ Tanium strongly recommends the host system have 10Gb network cards with chipsets from Intel for deployments over 70,000 endpoints.
² Calculate CPU cores based on only the physical cores from allocated CPUs—not the logical cores available with Hyper-Threading enabled.
³ Total space for Microsoft OS and Tanium Zone Server.

PostgreSQL Server

Contact your TAM for guidance on host computer specifications and PostgreSQL Server version specifications.

SQL Server

Use the following tables to estimate SQL Server host computer specifications and SQL Server version specifications. The columns indicate the total endpoints deployed.

Table 7:   Database server sizing
Edition Up to 500 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Microsoft SQL Server 2008 (64-bit)
Express1          
Workgroup        
Standard    
Enterprise
Data Center
SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 20172
Express1          
Standard      
Business Intelligence  
Enterprise

1 Proof-of-concept deployments only.

2 Tanium 7.2 and later only.

 

Table 8:   SQL Server host operating system sizing
Edition Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Microsoft Windows Server 2008 SP3 (64-bit)
Standard  
Enterprise
Data Center
Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Standard
Enterprise

The following hardware specifications are for use with Tanium Core Platform 7.x versions with archiving disabled. If you are using an older platform version (6.x), or you require archiving, consult your TAM for appropriate specifications.

Table 9:   SQL Server hardware sizing
Edition Up to 3,000 Up to 10,000 Up to 35,000 Up to 75,000 Up to 150,000 Up to 400,000
Server Device Physical or virtual Physical or virtual Physical or virtual Physical¹ Physical¹ Physical¹
CPU Core¹ 4 4 8 10 16 32
Memory 4 GB 8 GB 16 GB 24 GB 32 GB 48 GB
Disk Space² 125 GB 150 GB 200 GB 300 GB 500 GB 750 GB
Database Size 5 GB 20 GB 75 GB 150 GB 300 GB 500 GB
Disk Array IOPS <100 100 150 250 500 1000
¹ Calculate CPU cores based on only the physical cores from allocated CPUs—not the logical cores available with Hyper-Threading enabled.
² Total space for Microsoft OS and SQL Server. Microsoft recommends that the disk space available for memory dumps should be at least three times the amount of installed RAM. The required disk space for the OS and SQL Server takes into account the size of the OS, the size of the swap file, and the space required for memory dumps.

Most organizations achieve optimal performance using a single, internal RAID Array when Microsoft SQL Server transaction logging set to "Simple". If you plan to enable "Full" transaction logging, you may be required to provision an external RAID Array to manage the transaction logs.

To determine the specific disk drive performance characteristics and RAID configuration necessary to support deployments of different sizes, the table identifies the minimum Input/Output Operations per second (IOPS) for the database server. Using IOPS as the performance measurement enables internal storage administrators or storage vendors the flexibility to recommend a final disk configuration to provide optimal performance at the least cost.

The results reported and archived from each managed computer use an average of about 20 MB of data; however, storage requirements are directly related to platform usage patterns. Unless actual measurements confirm that the underlying disk infrastructure provides the minimum acceptable performance, we discourage the use of a Storage Attached Network (SAN) for the Tanium application server databases.

Last updated: 5/22/2018 3:03 PM | Feedback