Hardware sizing recommendations

Use the following hardware configurations as a reference to help you understand the hardware sizing requirements for using the BMC TrueSight IT Data Analytics product in your environment.

For more information, see Variables-that-impact-product-performance.

Notes

  • The following tests are carried out on a virtual setup using Intel® Xeon® CPU E5-2660 @ 2.20GHz processor and with a storage of 300 IOPS in the performance test lab. The performance of the product can vary depending on the type of storage and processor used for production configurations. The higher the storage and processor configuration, the better the performance.
  • All the results are based on the assumption that data records collected are of the size of 200 bytes per record.

The following configurations apply for both Windows and Linux systems and can be carried out by using both physical and virtual processors.

This topic contains the following information:

Related topics

Where to find more information

 Variables that affect sizing and scalability

 Component configuration recommendations

Nonproduction setups

This configuration is intended for nonproduction setups with one server. BMC recommends that you not use it for production environments.

 

Small setups

You can use the following configurations for a small setup with one server.

Scenario 1

The following table lists the configurations required for a small setup:

Scenario 2

The following table lists the configurations required for a small setup with relatively small storage:

Medium setups

You can use the following configurations for a medium setup.

Scenario 1

The following table lists the configurations required for a medium setup with five servers, distributed in the following way:

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

The following table provides configurations required for an individual server. You need to replicate the some configuration for all the other servers.

Scenario 2

The following table lists the configurations required for a medium setup with six servers, distributed in the following way:

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

This setup is for a relatively small storage and more number of concurrent users.

The following table provides configurations required for an individual server. You need to replicate the some configuration for all the other servers.

Large setups

You can use the following configurations for a large setup.

Note

Ensure that you use the same configurations to deploy components of the same type (for example, all Indexers).

Recommendation

If you want to perform a multiple-server deployment, by starting with installing all the product components on a primary computer, BMC recommends you to perform a custom installation (instead of a typical installation) to avoid performing manual configuration changes later.

Scenario 1

The following table lists the configurations required for a large setup with eleven servers, distributed in the following way:

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

The following table provides configurations required for an individual server. You need to replicate the some configuration for all the other servers.

Scenario 2

The following table lists the configurations required for a large setup with twelve servers, distributed in the following way:

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

This setup is for a relatively small storage and more number of concurrent users.

The following table provides configurations required for an individual server. You need to replicate the some configuration for all the other servers.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*