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 managed computers running Windows, macOS, Linux, or UNIX
- The number of saved questions that you configured to automatically archive results
- Whether the archived results for a given question are aggregated rather than stored as individual rows within the database
- The number of configuration, state, or property data elements that must be stored from each computer per saved question
- The size of each data element that is archived from managed computers
- The number of potential unique values that computers return for any given data element
- The frequency at which the data elements are archived
- The Tanium solutions you intend to use in addition to the Core Platform
Because the usage behavior is so different among customers, the requirements that the following tables present are based on representative data from numerous deployments ranging in size from less than 1,000 to more than 500,000 managed computers.
Use the following tables to estimate host system specifications for the Tanium Server. The columns indicate the total endpoints deployed. In a high availability (HA) deployment, each Tanium Server in the cluster must meet or exceed the requirements for the total number of endpoints that your deployment targets. (Each must be able to independently handle load from the full deployment in the event of failure.)
Use the following tables to estimate Tanium Module Server host system specifications. The columns indicate the total endpoints deployed.
Use the following tables to estimate Zone Server host system specifications. The columns indicate the number of endpoints reporting through the Zone Server. In a Zone Server HA deployment, provision each Zone Server to independently handle load for the cluster in case one HA peer fails.
Contact your TAM for guidance on host computer specifications and PostgreSQL Server version specifications.
Use the following tables to estimate SQL Server host computer specifications and SQL Server version specifications. The columns indicate the total endpoints deployed.
The following hardware specifications are for use with Tanium Core Platform 7.x versions with archiving disabled. If you use an older platform version (6.x), or you require archiving, consult your TAM for appropriate specifications.
Most organizations achieve optimal performance using a single, internal RAID array when Microsoft SQL Server transaction logging is set to Simple. If you plan to enable Full transaction logging, you might have 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, Table 9 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, the best practice is to not use a storage attached network (SAN) for the Tanium application server databases.
Last updated: 8/20/2019 1:19 PM | Feedback