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 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.
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 2698 v4 @ 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. IOPS is calculated based on the Bonnie++ metric, Random Seek/s.
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.
Use the following guidelines to size 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 test and small setup:
| Size | Daily Indexing volume | Data retention | Concurrent users |
|---|---|---|---|
| Test setup | 20 GB per day | 7 days | 2 |
| Small setup, scenario 1 | 100 GB per day | 14 days | 8 |
| Small setup, scenario 2 | 50 GB per day | 16 |
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 single-server sizing.
.
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.
Test setup
The following table lists the configurations required for a test setup with one server.
Note that this information is not intended for deploying the product in a production environment.
| Configuration support | Resources |
|---|---|
|
|
| (x 1 server) |
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.
| Configuration support | Resources |
|---|---|
|
|
| (x 1 server) |
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.
| Configuration support | Resources |
|---|---|
|
|
| (x 1 server) |
Notes to keep in mind
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.
| Number of Collection Agents | http.server.workers. | http.response. | agent.request.poll. |
|---|---|---|---|
| Upto 450 | (Default) 15 | (Default) 30,000 | (Default) 10 |
| More than 450 and upto 950 | 60 | 60,000 | 30 |
| More than 950 and upto 1750 Read more | 60 | 60,000 | 30 |
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.
Comments
Log in or register to comment.