Vertical scaling recommendations

This topic outlines the hardware capacity recommendations for vertically scaling the TrueSight IT Data Analytics product in your environment. 

Standard sizing guidelines

The hardware sizing guidelines are divided into four parts: test setups, small setups, medium setups, and large setups.

The test and small setup scenarios are recommended for a single-server deployment, while medium and large setup scenarios are recommended for a multiple-server deployment. You can also deploy the product in a single-server deployment and later vertically scale the product.

The following table lists the definitions of a medium and large setup:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it. 

Back to top

Small setup

Scaling your deployment is recommended only for medium and large setups while implementing a multiple-server deployment.

If you are operating in a small setup, you can deploy the product in a single-server environment. To understand the hardware recommendations for a single-server deployment (without scaling), see Single-server-sizing-recommendations.

Back to top

Medium setup, scenario 1

For a medium setup, you can use a configuration of one server for indexing 400 GB data per day, with a 14-day retention period, and with 8 concurrent users accessing the data.

The following table provides the resource configurations required for implementing this deployment.

Back to top

Medium setup, scenario 2

For a medium setup with a relatively smaller storage and more number of concurrent users, you can use a configuration of one server for indexing 200 GB data per day, with a 14-day retention period, and with 16 concurrent users accessing the data.

The following table provides the resource configurations required for implementing this deployment.

Back to top

Large setup, scenario 1

For a large setup, you can use a configuration of two servers for indexing 1 TB data per day, with a 14-day retention period, and with 8 concurrent users accessing the data.

Use the following guidelines for implementing this deployment:

• Component distribution
• Configuration recommendations

Component distribution

In this scenario, it is recommended to distribute the product components as follows:

• 1 server with one instance of the Indexer and Collection Station
• 1 server with one instance of the Indexer, Collection Station, Console Server, Search, and Configuration Database components

Configuration recommendations

The following table provides the resource configurations required for an individual server. You need to replicate the same configuration on the remaining servers.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

Back to top

Large setup, scenario 2

For a large setup with a relatively smaller storage and more number of concurrent users, you can use a configuration of two servers for indexing 500 GB data per day, with a 14-day retention period, and with 16 concurrent users accessing the data.

Use the following guidelines for implementing this deployment:

• Component distribution
• Configuration recommendations

Component distribution

In this scenario, it is recommended to distribute the product components as follows:

• 1 server with one instance of the Indexer and Collection Station
• 1 server with one instance of the Indexer, Collection Station, Console Server, Search, and Configuration Database components

Configuration recommendations

The following table provides the resource configurations required for an individual server. You need to replicate the same configuration on the remaining servers.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

Back to top

Notes to keep in mind

• Ensure that you use the same configurations to deploy components of the same type (for example, all Indexers, or all Collection Stations).
• If you want to perform a multiple-server deployment, by starting with a typical installation of all the product components on a primary computer, then it is recommended that you instead perform a custom installation with all the components selected. Doing this is important to avoid performing manual configuration changes later.

• This note is applicable only if you have configured Collection Agents by using the TrueSight console or the PATROL infrastructure. For optimum performance of such Collection Agents, you need to change certain properties based on the number of Collection Agents set up in your environment.

  The following properties need to be modified:

  • http.server.workers.thread.pool.size: Determines the maximum number of concurrent HTTP requests that can be handled by the Collection Station.
    This property needs to be added with the new values at %BMC_ITDA_HOME%\station\collection\custom\conf\agent.properties.
  • http.response.timeout.millis: Determines the period after which the Configuration Channel request must timeout.
    This property needs to be added with the new values at %BMC_ITDA_HOME%\agent\collection\custom\conf\agent.properties.
  • agent.request.poll.heartbeat.per.node.retry: Determines the number of failed HTTP requests before accepting that the Collection Station is not reachable.
    This property needs to be added with the new values at %BMC_ITDA_HOME%\agent\collection\custom\conf\agent.properties.

  Use the following table as a guideline to determine the preceding property values. These values are based on internal performance tests.

  Note

   If you are operating in an environment with 950-1750 Collection Agents, then at a minimum you need two Collection Stations setup on different servers to receive data from those Collection Agents.

  Back to top