Use the latest Deployment Sizing calculator spreadsheet, which is version 1.8.x. Using a version other than the latest may result in a diminished experience.
MAC users: You must use Microsoft Office version later than 15.19.1, otherwise some macros do not work.
What is the Deployment Sizing calculator?
The Deployment Sizing calculator lets you calculate the recommended deployment size and categorize the result as a small, medium, large, XLarge, 2XLarge, or 3XLarge deployment. You provide the sizing, such as the number of JVMs, web servers, and daily transactions. The spreadsheet also calculates the recommended bandwidth, Session Storage, and Performance Warehouse sizing.
The data provides the necessary guidance to make an accurate sizing decision. For more clarity, assess the results of the Deployment Sizing Calculator against the component sizing guidelines and customer examples provided in Assess Results.
Calculate sizing requirements
To use the Deployment Sizing calculator, follow these steps:
The spreadsheet may issue a warning that macros have been disabled. Click Enable Content before entering the requested sizing data.
Select the technologies to be used in deployment, then enter the requested sizing data for your environment in the Input Data worksheet. When entering data, the recommended deployment size and related sizing details automatically calculate on the spreadsheet.
Under Recommended deployment size, click a deployment size link (for example, Small, Medium, Large) to go to the applicable sizing page in the help for details about your deployment sizing recommendation. See Assess Results for more information.
Resolve No Sizing Issues
In certain scenarios, sizing calculations may not be feasible. This may happen if you enter too much load or too many agents. If this occurs, No sizing appears in a red background in the Recommended deployment size cell for the applicable deployment category.
Version 1.8 and later of the Deployment Sizing calculator lets you check and solve sizing issues. Click Perform sizing check either under the Recommended deployment size section or in the Sizing check worksheet to see potential sizing issues. Problems are tagged with red. Click the related link to see where the issue occurs in the Scenarios worksheet.
The Scenarios worksheet covers all important KPIs and input data results. A red cell background color indicates that you should check the accuracy of your input values.
Potential input sizing issues include:
- Transactions per Second (tps): There are too many transactions for the assumed average node length. Check and adjust the server load.
- Peak transactions per Second (peak tps): Transactions caused by the peak are too high.
- Total agents: You reached or exceeded the maximum allowed connected agents per server.
- Max. tps for XY system profiles: System Profiles require resources. Avoid having too many if possible. The more System Profiles, the greater impact on the server throughput.
- Measures: The Server has to handle too many cyclic measures generated by Agents.
- Nodes per Second (nps): The limit of maximum nodes per second is reached or exceeded.
- Peak nodes per Second (peak nps): The limit of maximum nodes per second during peak is reached or exceeded.
- Collectors: Your sizing reached or exceeded the maximum number of Collectors (60) for a single Server.
- Concurrent visits: UEM only. The maximum number of concurrent visits is reached or exceeded.
Ensure sizing accuracy
Use the sizing computations in the Result Details worksheet to ensure sizing estimates are in line with actual sizing data, and get to additional help on network bandwidth sizing and disk I/O guidelines.
Next : Assess Results