The Project Life represents the estimated time (in years) from the initial server deployment to its end-of-life (either through refresh or application EOL).
Failover models a high availability configuration. It reserves capacity on each server to account for the workload of the paired server in a 2 node cluster in event of an occurrence making the paired server inoperable.
As server utilization increases, application response time typically degrades, increasing the risk of not meeting service level agreements (SLAs). Max Utilization allows you to model your maximum projected utilization for each server resource to ensure your server sizing meets SLA requirements over the entire project life. Raising this value increases the risk of not meeting SLAs.
The Peak-to-Average ratio reserves system headroom required for workload spikes during peak application usage periods. For example, if your month-end close drives 50% more load than average, then your peak-to-average ratio should be 1.5.
The YoY (year over year) Growth Rate models how much (on average) your workload requirements grow each year based on business needs. This value could also be referred to as the Compound Annual Growth Rate (CAGR) - the amount you expect your workload to grow over the project's life.
The Baseline server is the server configuration you are most familiar with for the application workload you are modeling. The tool compares the Baseline server data against data entered in the Advanced mode to create a comparison for future utilization needs.
CPU Description provides a simplified configuration for the processor being modeled. It includes the number of processors supported (2P = 2 processor, 4P = 4 processor, etc) and the specific processor model being used for the selected server configuration. The description is simplified for display and provides only the frequency, number of cores, and cache size that are unique to that processor model. For more detailed information about Intel Xeon processors visit http://ark.intel.com.
CPU Performance is an estimate of the server performance for the modeled workload. The modeling tool defaults to specINTRate 2006* - a benchmark commonly used as a measure of performance for a variety of compute intensive workloads. If desired, you can replace these defaults with measures more appropriate for your workload and environment. REMINDER: if you change the performance benchmark for one server configuration (i.e. Baseline), you must also change the performance for the other 2 server configurations in the Advanced mode. This is necessary for the tool to properly project estimated utilization numbers for those server configurations.
The memory capacity in GB installed on the selected server.
The number of I/O slots available on the selected server.
Initial Average Utilization represents the average consumption by resource type of your modeled workload on the reference server.
Alternate A is the first alternative server configuration to be compared to the Baseline server for your projected workload.
The processor configuration for the selected server - this will specify the number of processors as well as the processor model. The processor model uniquely identifies the selected processor type which maps to specific number of cores, frequency, memory bandwidth and cache size that are unique to that processor model.
CPU Performance is an estimate of the server performance for the modeled workload. The modeling tool defaults to specINTRate 2006* - a benchmark commonly used as a measure of performance for a variety of compute intensive workloads. If desired, you can replace these defaults with measures more appropriate for your workload and environment. REMINDER: if you change the performance benchmark for one server configuration (i.e. Baseline), you must also change the performance for the other 2 server configurations in the Advanced mode. This is necessary for the tool to properly project estimated utilization numbers for those server configurations.
The memory capacity in GB installed on the selected server.
The number of I/O slots available on the selected server.
The initial average utilization for alternate servers A and B is calculated based on the initial average utilization for the reference server and the relative capacities of the alternate servers (relative to the reference server).

For instance, if alternate server A has double the compute capacity of the reference server, then the initial average CPU utilization of alternate server A will automatically be set at half the value on the reference server.

Conversely, if the initial average CPU utilization on the reference server is increased to be double the original default average utilization setting, then the initial average CPU utilization of the alternate servers will automatically be doubled as well to reflect the increased intensity of the workload.
Alternate B is the second alternative server configuration to be compared to the Baseline server for your projected workload.
The processor configuration for the selected server - this will specify the number of processors as well as the processor model. The processor model uniquely identifies the selected processor type which maps to specific number of cores, frequency, memory bandwidth and cache size that are unique to that processor model.
CPU Performance is an estimate of the server performance for the modeled workload. The modeling tool defaults to specINTRate 2006* - a benchmark commonly used as a measure of performance for a variety of compute intensive workloads. If desired, you can replace these defaults with measures more appropriate for your workload and environment. REMINDER: if you change the performance benchmark for one server configuration (i.e. Baseline), you must also change the performance for the other 2 server configurations in the Advanced mode. This is necessary for the tool to properly project estimated utilization numbers for those server configurations.
The memory capacity in GB installed on the selected server.
The number of I/O slots available on the selected server.
The initial average utilization for alternate servers A and B is calculated based on the initial average utilization for the reference server and the relative capacities of the alternate servers (relative to the reference server).

For instance, if alternate server A has double the compute capacity of the reference server, then the initial average CPU utilization of alternate server A will automatically be set at half the value on the reference server.

Conversely, if the initial average CPU utilization on the reference server is increased to be double the original default average utilization setting, then the initial average CPU utilization of the alternate servers will automatically be doubled as well to reflect the increased intensity of the workload.
Select from a variety of output views to aid in decision making and modeling. By default, projections for all 3 server configurations are shown in chart form. To compare only 2 servers, uncheck the configuration you wish to ignore. To see more detail on resource utilization projections, click the appropriate magnifying glass. To see detailed utilization projection data, switch to table view.
CSS Check