Single-server sizing recommendations

Depending on your business needs you can deploy the product in a single-server environment or a multiple-server environment. Alternatively, you can start with a single-server deployment and as your business needs increase, you can scale your deployment either horizontally or vertically.

This topic outlines the hardware capacity recommendations for sizing the BMC TrueSight IT Data Analytics product in a single-server environment. For recommendations on tuning the individual components, see Component-configuration-recommendations-for-single-server-sizing.

Related topics

Where to find more information

Component configuration recommendations

FAQs-about-performance-and-scalability

Notes

  • The sizing recommendations outlined in this topic are for reference purposes only. These recommendations are meant to be used as a guide for determining your environment-specific sizing estimates.
  • The sizing estimates provided in this topic are based on performance tests carried out on a virtual setup using Intel® Xeon® CPU E5-2660 @ 2.20GHz processor, with a storage of 300 IOPS. All the results are based on the assumption that data records collected are of the size of 200 bytes per record.
  • 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.

This topic contains the following hardware recommendations and guidelines that you can use as a reference to size your environment:

Standard sizing guidelines

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

The nonproduction 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 nonproduction and small setup:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.

Hardware recommendations

Single-server deployments are recommended for a non-production setup or small setup. In a single-server deployment, one instance of the product can handle the entire process of collecting data, indexing it, and finally making it available for search.

Hardware sizing for a single-server setup involves planning your hardware capacity and tuning the configuration of the product components. The component configurations are necessary to ensure optimal use of resources available. For more information, see Component-configuration-recommendations-for-horizontal-scaling.

Use the following hardware recommendations for a single-server deployment. These configurations apply for both Windows and Linux systems and can be carried out by using both physical and virtual processors.

Nonproduction setup

The following table lists the configurations required for a nonproduction setup with one server.

Note that this information is not intended for deploying the product in a production environment.

Small setup, scenario 1

The following table lists the resource configurations required for indexing 100 GB per day, with a 14-day retention period, and with 8 concurrent users accessing the data.

Small setup, scenario 2

The following table lists the resource configurations required for a small setup with a relatively smaller storage and more number of concurrent users. This configuration aims at indexing 50 GB per day, with a 14-day retention period, and with 16 concurrent users accessing the data.

 

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