Page tree
    Skip to end of metadata
    Go to start of metadata

    This topic outlines the hardware capacity recommendations for horizontally scaling the TrueSight IT Data Analytics product in your environment. For recommendations on tuning the individual components, see Component configuration recommendations for horizontal scaling.

    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. 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.

    • If you enable Indexer redundancy in your environment, you need double the resources stated in this topic. This means you need to add additional servers with the same configuration as that recommended in this topic for various kinds of setups.

    Use the following recommendations to plan the hardware capacity required for horizontally scaling your deployment.

    Standard sizing guidelines

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

    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:

    SizeDaily Indexing volumeData retentionConcurrent users
    Medium
    Scenario 1400 GB per day14 days8
    Scenario 2200 GB per day16
    Large
    Scenario 11 TB per day14 days8
    Scenario 2500 GB per day16
     

    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, a configuration of five servers is recommended for indexing 400 GB data per day, with a 14-day retention period, and with 8 concurrent users accessing the data.

    Use the following guidelines for implementing a medium size deployment.

    Component distribution

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

    • 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

    Configuration recommendations

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

    Configuration supportResources
    • Indexing volume: 400 GB per day
    • Data retention period: 14 days
    • Number of concurrent users: 8
    • Number of data collectors: 6,000
    • Number of managed hosts: 2,000
    • CPU: 8
      (x 5 servers)
    • RAM: 16 GB
      (x 5 servers)
    • Disk space:
      • Server hosting the Indexer: 3500 GB (or 3.5 TB)
        (x 2 servers)
      • Server hosting components other than the Indexer: 500 GB
        (x 3 servers)

    If you want to retain data for longer than 14 days, then the RAM and disk space configurations need to be increased. For more information, see Long-term data retention recommendations.

    Back to top

    Medium setup, scenario 2

    For a medium setup with a relatively smaller storage and more number of concurrent users, a configuration of three servers is recommended. This setup aims for indexing 200 GB data per day, with a 14-day retention period, and with 16 concurrent users accessing the data.

    Component distribution

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

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

    Configuration recommendations

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

    Configuration supportResources
    • Indexing volume: 200 GB per day
    • Data retention period: 14 days
    • Number of concurrent users: 16
    • Number of data collectors: 3,000
    • Number of managed hosts: 1,000
    • CPU: 8
      (x 3 servers)
    • RAM: 16 GB
      (x 3 servers)
    • Disk space:
      • Server hosting the Indexer: 1200 GB (or 1.2 TB)
        (x 2 servers)
      • Server hosting components other than the Indexer: 500 GB
        (x 1 server)

    If you want to retain data for longer than 14 days, then the RAM and disk space configurations need to be increased. For more information, see Long-term data retention recommendations.

    Back to top

    Large setup, scenario 1

    For a large setup, a configuration of eleven servers is recommended for indexing 1 TB data per day, with a 14-day retention period, and with 8 concurrent users accessing the data.

    Component distribution

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

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

    Configuration recommendations

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

    Configuration supportResources
    • Indexing volume: 1 TB per day
    • Data retention period: 14 days
    • Number of concurrent users: 8
    • Number of data collectors: 15,000
    • Number of managed hosts: 3,000
    • CPU: 8
      (x 12 servers)
    • RAM: 16 GB
      (x 12 servers)
    • Disk space:
      • Server hosting the Indexer: 3500 GB (or 3.5 TB)
        (x 6 servers)
      • Server hosting components other than the Indexer: 500 GB
        (x 6 servers)

    If you want to retain data for longer than 14 days, then the RAM and disk space configurations need to be increased. For more information, see Long-term data retention recommendations.

    Back to top

    Large setup, scenario 2

    For a large setup, a configuration of seven servers is recommended for indexing 500 GB data per day, with a 14-day retention period, and with 16 concurrent users accessing the data.

    Component distribution

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

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

    Configuration recommendations

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

    Configuration supportResources
    • Indexing volume: 500 GB per day
    • Data retention period: 14 days
    • Number of concurrent users: 16
    • Number of data collectors: 7,500
    • Number of managed hosts: 1,500
    • CPU: 8
      (x 7 servers)
    • RAM: 16 GB
      (x 7 servers)
    • Disk space:
      • Server hosting the Indexer: 1600 GB (or 1.6 TB)
        (x 4 servers)
      • Server hosting components other than the Indexer: 500 GB
        (x 3 servers)

    If you want to retain data for longer than 14 days, then the RAM and disk space configurations need to be increased. For more information, see Long-term data retention recommendations.

    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.

      Number of Collection Agentshttp.server.workers.
      thread.pool.size
      http.response.
      timeout.millis
      agent.request.poll.
      heartbeat.per.node.retry
      Upto 450(Default) 15(Default) 30,000(Default) 10
      More than 450 and upto 9506060,00030
      More than 950 and upto 1750
      Read more
      60 60,00030

      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

    Where to go from here

    To ensure optimal use of resources, you need to tune some of the configuration settings (such as the initial memory and maximum memory required) for each of the product components. For more information, see Component configuration recommendations for horizontal scaling.