Sizing App Visibility Manager and Synthetic TEA Agent components



The values provided in this topic are estimations, meant as general guidelines for an out-of-the-box configuration, and they do not take all contributing factors (such as the number of metrics and events) into account. If you have values in any of the listed categories that are exceptional, then you should consult with BMC Support. You must monitor your data in the first few days, and based on your results, adjust the database retention period, database size, number of App Visibility collectors, or installed hardware.

Maximum number of components per deployment

Apply the following guidelines to your deployment, per tenant:

  • Maximum number of App Visibility agents or synthetic TEA Agents per App Visibility collector = 100
  • Maximum number of App Visibility collectors per App Visibility portal = 5
  • Maximum number of App Visibility agents or synthetic TEA Agents per App Visibility portal = 500 (divided among 5 App Visibility collectors)
  • Maximum number of App Visibility portals per Presentation Server (per tenant) = 1


Minimum requirements for App Visibility server component installation

If all App Visibility server components are installed together, such as for a very small environment or a test environment, approximately 2.1 GB of disk space is required and 12 GB RAM. The RAM requirement for a system where all the component are installed is less than the sum in the following table because the portal and collector share a database in a combined system.

Minimum requirements for App Visibility server components that are installed on separate computers

ComponentFree disk spaceMinimum RAM
Collector2 GB4 GB (8 GB recommended)
Portal2 GB4 GB (8 GB recommended)
(Optional) Proxy220 MB6 GB (8 GB recommended)

The App Visibility proxy is used for end-user monitoring. It is not required for synthetic monitoring.

You can configure only one App Visibility portal per tenant with the Presentation Server. For deployment guidance, see also Operations Management basic deployment with App Visibility Manager and Operations Management service provider and tenant deployment.

Hardware sizing for App Visibility deployments

Based upon the calculated size of your deployment, select the appropriate equipment for optimum performance.

Database size calculations assume a retention period of 35 days.

App Visibility collector resources for different deployment sizes

BMC recommends that all nodes in TrueSight App Visibility Manager Proxy cluster have approximately the same disk size.


Size of deployment

Number of agents

CPUs required

Memory required

Database size

Small

20

2 CPUs, 2 GHz each

8 GB RAM

200 GB

Medium

100

2 CPUs, 2 GHz each

8 GB RAM

1000 GB

Large

200

4 CPUs, 2 GHz each

16 GB RAM

2000 GB*

*Divide the required disk size between the number of collectors: <diskSize> / <numberOfCollectors>

To install the App Visibility collector software and database, the computer must have approximately 2 GB of free disk space and a minimum of 4 GB RAM (8 GB recommended).

The App Visibility collector database must be scaled for the number of App Visibility agents in your environment. To calculate the maximum database size, use the following equation:

10 GB x number of agents = maximum database size

The default maximum database size is 100 GB, which is enough for 10 App Visibility agents in an average environment. For information about changing the App Visibility collector database settings, see Managing the App Visibility database .

App Visibility portal resources for different deployment sizes

Size of deployment

Number of agents

CPUs required

Memory required

Database size

Small

20

2 CPUs, 2 GHz each

8 GB RAM

20 GB

Medium

100

2 CPUs, 2 GHz each

8 GB RAM

100 GB

Large

200

4 CPUs, 2 GHz each

16 GB RAM

200 GB

To install the App Visibility portal software and database, the computer must have approximately 2 GB of free disk space and a minimum of 4 GB RAM (8 GB recommended).

Disk space requirements are the same, even if many App Visibility collectors are used.

App Visibility proxy resources for different deployment sizes

Size of deployment

Number of requests

Number of nodes

CPUs required

Memory required

Disk size

Small

up to 10 per second

1*

4 CPUs, 2 GHz each

6 GB RAM

50 GB

Mediumup to 500 per second24 CPUs, 2 GHz each8 GB RAM100 GB
Largeup to 2000 per second34 CPUs, 2 GHz each16 GB RAM200 GB

*For high availability, more than one proxy node is required.

To install the App Visibility proxy software, the computer must have approximately 220 MB of free disk space and a minimum of 6 GB RAM (8 GB recommended).

 

Sizing for Synthetic Monitor components

Synthetic TEA Agent sizing

A single synthetic TEA Agent can process up to 120 Execution Plans when the Execution Plan references a single web-based script. This limit is set by the system.

If your scripts produce a high volume of user-interface transactions, such as browser-driven scripts, BMC recommends that you limit the TEA Agent to 50 scripts.

There is no limit to the number of TEA Agents that you can install on a single computer.

For information about Execution plans, see Editing an application's synthetic settings .

Hardware sizing for Synthetic Monitor deployments

Based upon the calculated size of your deployment, select the appropriate equipment for optimum performance.

Database size calculations assume a retention period of 35 days.

App Visibility portal database resources for different deployment sizes for synthetic transactions

Size of deployment

CPUs required

Memory required

Database size

Small

2 CPUs, 2 GHz each

8 GB RAM

2 GB

Medium

2 CPUs, 2 GHz each

8 GB RAM

10 GB

Large*

4 CPUs, 2 GHz each

16 GB RAM

20 GB

*For large deployments, increase the heap size on your portal to 4 GB. See Changing the heap size on App Visibility components for more details.


Calculations are for transactions using the URLChecker script, with 10 custom timers or page timers per transaction, and approximately 20% of transactions with 1 error each. For transactions that don't use timers and have fewer errors, database size requirements may be smaller.


App Visibility collector database resources for different deployment sizes for synthetic transactions

Size of deployment

Number of transactions per hour**

CPUs required

Memory required

Database size

Small

15000

2 CPUs, 2 GHz each

8 GB RAM

20 GB

Medium

75000

2 CPUs, 2 GHz each

8 GB RAM

100 GB

Large*

120000

4 CPUs, 2 GHz each

16 GB RAM

200 GB

*For large deployments, increase the heap size on your collector to 4 GB. See Changing the heap size on App Visibility components for more details.

**If you are likely to exceed the number of transactions per hour, BMC recommends you add an additional collector to your deployment.


Calculations are for transactions using the URLChecker script, with 10 custom timers or page timers per transaction, and approximately 20% of transactions with 1 error each. For transactions that don't use timers and have fewer errors, database size requirements may be smaller.

Calculations assume approximately 10% of transactions generate events. Sustained peaks of event generation and fluctuating event levels can adversely affect performance.


Was this page helpful? Yes No Submitting... Thank you

Comments