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

BMC TrueSight Capacity Optimization components are designed to enable you to scale the BMC TrueSight Capacity Optimization infrastructure to manage environments with varying numbers of managed systems, data feeds, reports, and users, and amounts of historical data.

Sizing drivers

The following figure shows the major sizing drivers for each BMC TrueSight Capacity Optimization component:

BMC TrueSight Capacity Optimization sizing drivers

A major sizing driver for the BMC TrueSight Capacity Optimization infrastructure is the required throughput for processing collected samples. One BMC TrueSight Capacity Optimization unit refers to one million samples per day. For example, 20 million samples per day are also referred to as 20 BMC TrueSight Capacity Optimization units.

The following table shows how to translate the number of managed entities, metrics, and time granularity of the samples into the number of samples per day.

Number of managed entities

Average number of metrics per entity

Time granularity of the samples

Samples for 24 hours

1,250

40

15 minutes

5 million

2,500

40

30 minutes

5 million

5,000

40

1 hour

5 million

An entity is a managed system or device whose performance data is collected, such as a physical stand-alone server, a partition on a server, a virtual server, a database instance, a storage element, or a network element.

Note

The preceding table does not take into account business driver metrics. Estimate the number of business driver metric samples that have to be processed on a daily basis as 10% of the overall managed entity metric samples per day.

The following topics describe guidelines and recommendations for sizing each BMC TrueSight Capacity Optimization component, based on average utilization scenarios. All sizing values are provided as general guidance.

Recommendation

Contact Customer Support for assistance in sizing BMC TrueSight Capacity Optimization.

Deployment size

The following figure shows BMC TrueSight Capacity Optimization deployment sizes according to the two major sizing drivers: the number of managed entities and the number of samples to process.

Deployment sizes

Note the following information:

  • The figure is intended as a guideline only. BMC recommends contacting Customer Support when sizing a BMC TrueSight Capacity Optimization deployment.
  • The figure does not represent the full range of scalability options.
  • For the Application Server and ETL Engine server components, in spite of the general guidelines regarding multiple servers, other considerations can dictate using a single (physical) server configured with an adequate amount of resources. These considerations, for example, can be operational or related to maintenance. This consideration does not alter the guidelines regarding separate servers for the separate components.
  • These deployments are based on average utilization and default aging policies.

Note

The current compatibility offering for the PostgreSQL database supports large environments handling up to 50 million records per day.

Sizing the Presentation Server

The Presentation Server is a modern, web-based user interface technology integrated throughout the TrueSight product suite. In this release of TrueSight Capacity Optimization, this component hosts the OOTB Capacity Pools view. Access to the TrueSight Presentation Server component is enabled through integrated system authentication with BMC Atrium Single Sign-On. Any Atrium SSO user authorized to access the OOTB Capacity Pools View, can login to this component.

For guidelines and recommendations to help you size the Presentation Server, see Sizing the Presentation Server .

3 Comments

  1. I recommend that the need for a TSPS server is included in the diagram: it is currently not (the picture is from 2011) and that picture is used too often by people in a rush to order HW without reading documentation.

    1. Hello Renato,

      Thank you for your feedback. We will work with the R&D team to address your comment.

      Thanks,

      Alka 

  2.