Consider the following sizing and scalability guidelines when planning your BMC TrueSight App Visibility Manager deployment. These guidelines also apply to deployment of BMC Synthetic Transaction Execution Adapter (TEA) Agents.
Note
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 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.
The App Visibility collector database must be scaled to 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 agents in the aforementioned environment. For information about changing the App Visibility collector database settings, see Changing App Visibility collector settings.
Apply the following guidelines to your deployment, per tenant:
To install the App Visibility collector software and database, the computer must have approximately 2 GB of free disk space.
If all components are installed together, approximately 2.1 GB of disk space is required.
Disk space requirements for the App Visibility portal software and database are the same, no matter how many App Visibility collectors are used.
To install the App Visibility portal software and database, the computer must have approximately 2 GB of free disk space.
If all components are installed together, approximately 2.1 GB of disk space is required.
To install the App Visibility proxy software, the computer must have approximately 400 MB of free disk space.
If all components are installed together, approximately 2.1 GB of disk space is required.
Only one App Visibility portal can be configured 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.
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.
Based upon the calculated size of your deployment, select the appropriate equipment for optimum performance.
App Visibility server resources for different deployment sizes—without synthetic transactions Size of deployment Number of agents CPUs required Memory required Disk 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 Extra Large 500 8 to 16 CPUs, 2 GHz each 32 GB RAM 5000 GB* * Divide the required disk size by the number of collectors: <diskSize> / <numberOfCollectors> App Visibility server resources for different deployment sizes—with synthetic transactions Size of deployment Number of transactions per hour CPUs required Memory required Database size Small 12000 2 CPUs, 2 GHz each 8 GB RAM 20 GB Medium 60000 2 CPUs, 2 GHz each 8 GB RAM 100 GB Large 120000 4 CPUs, 2 GHz each 16 GB RAM 200 GB Extra Large 300000 8 to 16 CPUs, 2 GHz each 32 GB RAM 500 GB Calculations are for transactions with ten custom timers or page timers per transaction. For transactions that don't use timers, database size requirements may be smaller. Database size calculations assume a retention period of 35 days.
System requirements for App Visibility
Preparing for the App Visibility server installation
Configuring App Visibility after installation
BMC TrueSight Operations Management basic deployment
4 Comments
Michael Evans
please update the Portal Sizing description to include information about the sizing of the database for the Portal (vs. the collector)
Benjie Wolicki
Thanks for the feedback Michael. The numbers on this page are due for an update soon. I will add this to the update.
Bao Phac Do
Sara Kamen