BMC TrueSight Capacity Optimization - Analyze€¦ · Analyze processes operating system and applications data from multiple systems and creates a multiple workload representation

Analyze

BMC TrueSight Capacity Optimization

URL:Date: 2017-07-31 00:59

https://docs.bmc.com/docs/x/-ItBH

BMC TrueSight Capacity Optimization Page of 2 48

ContentsAnalyze best practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Before you begin using workloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Benefits of using Analyze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Tips for creating useful workloads with a Windows Gateway Server . . . . . . . . . 5Using Analyze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Ad-hoc data collection and analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Displaying data in Analyze from Oracle partitioned systems . . . . . . . . . . . . . . . . 6Viewing and displaying VMware data in Analyze . . . . . . . . . . . . . . . . . . . . . . . . 7

VMware Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8VMware Memory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10VMware Disk Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11VMware Per Processor Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Viewing HP IVM data in Analyze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Workload and Predict model characterization in Analyze . . . . . . . . . . . . . . 15

Viewing results for a Xen system in Analyze . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Types of Analyze workloads when using a Windows Gateway Server . . . . . . . 19Windows console Analyze reports and what they mean . . . . . . . . . . . . . . . . . . 20Analyze outputs from a Windows Gateway Server . . . . . . . . . . . . . . . . . . . . . . 21Using Analyze to do workload characterization . . . . . . . . . . . . . . . . . . . . . . . . . 22

Characterizing the workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Administering Analyze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Additional information about analysis intervals on a Windows Gateway Server . . 26

Restrictions on the analysis interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Criteria for interval selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Creating and using workload characterizations . . . . . . . . . . . . . . . . . . . . . . . . . 29Creating a standard workload characterization file . . . . . . . . . . . . . . . . . . . 30Selecting an appropriate analysis interval with a Windows console . . . . . . 31Analyzing the collected data using a Windows console . . . . . . . . . . . . . . . . 33Viewing Analyze reports using a Windows console . . . . . . . . . . . . . . . . . . . 34Using the Analyze cut-disk option on a Windows Gateway Server . . . . . . . 41

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46


This section provides general information about workloads and tips on creating useful workloads using the Windows Gateway Server. It also includes examples that demonstrate different options in creating and refining workloads.

A system normally performs a large number of transactions in any given time period. While the response time of individual transactions can be different, analyzing the response time of individual transactions is very resource consuming, tedious and generally uninformative. For typical performance analysis, reporting or planning purposes, it is usually the overall performance of a collection of transactions that is most important. In BMC Performance Assurance, such a collection is called a . In this section, we will use the Analyze component to create workloads that workloadwill then be used either for reporting or modeling.

A workload represents a stream of transactions that are initiated by one or more users. These transactions often have different performance characteristics; that is, they have very different resource consumption characteristics or service demands.

Because different groups of users can run different collections of transactions, you might also be interested in dividing system activity into multiple workloads. Such workloads can be defined by applications, user groups, departments, databases, and so on.

Analyze processes operating system and applications data from multiple systems and creates a multiple workload representation of the activities on such a distributed system. Such a representation of the system and the activities on it is called a system performance model.

For more information, see:

Analyze best practices (see page 3)Using Analyze (see page 6)Administering Analyze (see page 26)

Analyze best practicesFor information on Analyze best practices, see:

Before you begin using workloads (see page 3)Benefits of using Analyze (see page 5)Tips for creating useful workloads with a Windows Gateway Server (see page 5)

Before you begin using workloadsYou must have already collected data on the computers you want to analyze prior to creating workloads. For information about collecting data, see .Collecting data using Gateway Server


The following figure shows the Analyze data flow.

Analyze data flow


1.

2.

3.

4.

Benefits of using AnalyzeAnalyze provides the following benefits:

The ability to create a variety of reports and save them in HTML format for viewing through a web browser.A way to identify problem areas and any performance bottlenecks requiring further investigation.A tool for identifying groups of users and types of work used to define workloads.A facility to create a model for a more powerful analysis and to perform studies What if...?using Predict.

Analyze uses the Windows performance registry information and the UNIX kernel information gathered by the data collectors as its performance measurement data sources for characterizing system workloads.

Analyze uses the workload characterization file ( ) that you create using the Analyze GUI to .ansupply the input model definition.

Tips for creating useful workloads with a Windows Gateway ServerThis section describes some general tips for creating useful workloads. A useful workload is one that shows pertinent information in either the Analyze reports or in the Predict model.

Tips for creating useful workloads

Tip Description

Plan ahead and know what you want to do

For example, do you want to create a workload for the purpose of viewing reports or for creating a model? Knowing ahead of time will save a lot of time in the long-run. Modeling gets much attention, but only doing reporting is valid for many situations In reality you usually track much more than you model. Creating the model takes less time if you have done the planning ahead of time. If you don't know whether you want to report or model, run through the data and see if anything stands out.

Use the 80/20 rule

Essentially, this means don't get lost in the details. Find out what is important, then dig into the details. Usually, a couple of categories will find 80% of the activity. Spend your time analyzing that 80% instead of spending your time on the 20%.

Keep the number of workloads low

Two workloads is a good rule of thumb. In some instances, more than two might be necessary but if you have too many, it is more difficult to find the information you need.

Watch zzz

The zzz workload shows everything that has not been put into a workload that you create. If there is too much in zzz, it means the workloads you have created are not the best representation of your data.


1.

2.

3.

For information about the reports available, see Windows console Analyze reports and what they .mean (see page 20)

Using AnalyzeFor information on using Analyze, see:

Ad-hoc data collection and analysis (see page 6)Displaying data in Analyze from Oracle partitioned systems (see page 6)Viewing and displaying VMware data in Analyze (see page 7)Viewing HP IVM data in Analyze (see page 15)Viewing results for a Xen system in Analyze (see page 17)Types of Analyze workloads when using a Windows Gateway Server (see page 19)Windows console Analyze reports and what they mean (see page 20)Analyze outputs from a Windows Gateway Server (see page 21)Using Analyze to do workload characterization (see page 22)

Ad-hoc data collection and analysisCollecting data and viewing performance reports and charts on an ad-hoc basis requires:

Using Collect to specify systems from which to collect data, specifying collection and summarization intervals, and scheduling the collections.Using one of the following:

Using Analyze and its default workload characterization to process collected data and create Visualizer input files, Analyze reports, and a default model.orCreating a custom workload characterization in Analyze to focus reports and the model on transaction classes and workloads you are interested in, then re-analyzing the data.

Viewing performance reports and charts in Analyze.

Displaying data in Analyze from Oracle partitioned systemsFor Oracle partitioned systems, Analyze groups the systems according to the physical hardware on which they are installed, and displays this information in the Analyze - Physical System Report as shown in the following figure.

Analyze - Physical System Report for Oracle partitions


When a System Controller is part of a data collection and is included in the list for processing, Analyze detects if there are any missing partitions from the current processing and displays in N/Athe columns for those systems. This information helps you understand if there are any additional partitions that should be included, helping you form a complete understanding of the partitioned environment.

Viewing and displaying VMware data in AnalyzeThe following Analyze reports present information specific to VMware, including configuration and resource consumption:

VMware Summary Report (see page 8)VMware Memory Report (see page 10)VMware Disk Report (see page 11)VMware Per Processor Report (see page 13)

In these reports, each VM is identified by its display name used by VMware, and the guest operating systems are also displayed. Each operating system instance, including the VMware service console operating system, is shown as an independent computer. For more information about these reports, refer to the Analyze online Help.

First, you must create a workload characterization file that includes the VMware service console, and optionally the virtual machines, as computers. An Analyze workload characterization contains parameters for doing the following

Creating a performance model for use by PredictViewing charts of performance dataCreating performance reports


1. 2. 3. 4.

5.

When you run Analyze, it uses the workload characterization to evaluate collected performance data, and create a performance model, reports, and, optionally, Visualizer input files.

To generate the VMware reports, perform the following steps:

Right-click Analyze in the Tree view, and select .Open Workload CharacterizationSelect the appropriate workload characterization ( ) file for the VMware system..anReview the displayed interval or set another interval.Run Analyze by clicking on the green arrow in the menu bar, or right-click the Workload Characterization in the Tree view and select .Start AnalyzeExpand the Reports item and then expand the VMware selection.

VMware Summary ReportUse this report to view summary information for the VMware service console and the VMs (identified by display name) for the system, as shown in the following figure.

Analyze VMware Summary Report

The following table describes each of the columns in the report. You might need to scroll to the right to see some of the report columns.

Column Description


Column Description

VMware Console Name

The name of the VMware service console that provides all of the management functions for the VMs. For reporting purposes, this name is used to refer to the physical host computer.

Display Name

This value is used to refer to the VM. Each VM is identified by its display name specified in the VMware configuration file. The display name is not guaranteed to be unique on the VMware server. BMC Performance Assurance does not support duplicate VM display names within a VMware server. VMs with the same display name are treated as one.

Guest OS

The operating system type installed as a guest OS on the VM. Each VM can run Microsoft Windows or Linux as guest OSs.

Physical Procs

The number of physical processors on the ESX server system. This value is shown only for the top-level server information.

Logical Procs

The number of logical processors on the ESX server system. This value is shown only for the top-level server information.

Virtual Procs

The number of CPUs allocated to the VM. This value is shown for each VM.

System Service

The total reported overhead usage for all VMs, due to virtualization. The CPU utilization attributed to the VMware host on behalf of the VMs.

CPU Util The percentage of CPU time used by a VM. The CPU usage shown in this column is a physical value; it represents the total CPU usage of the amount of CPU that has been allocated for the VM.

CPU Shares

The number of CPU shares assigned to a VM.

CPU Min The guaranteed minimum CPU percentage reserved for this VM.

CPU Max

The maximum CPU percentage for a VM. The valid range of values is from zero ("0") to the number representing the total physical CPU resources. The maximum can be greater than 100 for SMP virtual machines that use more than one full physical CPU.

CPU Ready

The percentage of time during the measurement session that the VM was ready to process transactions, but could not get scheduled to run on a physical CPU.

CPU Effective

The percentage (out of 100%) of the maximum physical CPU resource allocated to the VM that it is currently using.

Total Memory

The amount of RAM (in MB) for the physical computer. This value is shown only for the top-level VMware service console row.

Shared Memory

The memory required for single copy of memory shared between VMs.

Swapped Memory

The sum of all currently swapped memory for running VMs. This value is equivalent to swapout-swapin.

Guest Memory Config

Amount of memory allocated for the VM (in MB).


VMware Memory ReportUse this report to view memory statistics for the VMs (identified by display name) as shown in the following figure.

Analyze VMware Memory Report

The following table describes each of the columns in the report:Column Description

VMware Console Name


Display Name

This value is used to refer to the VM. Each VM is identified by its display name specified in the VMware configuration file. This display name is not guaranteed to be unique on the VMware server. BMC Performance Assurance does not support duplicate VM display names within a VMware server. Virtual machines with the same display name are treated as one.

Memory Shares

The total number of memory shares assigned to a VM.

Shared Memory

The amount of memory in MB that is shared through transparent page sharing either within a VM or with other VMs running on the same server.

Memory Used

The amount of memory in MB actively used by a VM.

Overhead Memory

The overhead memory in MB for the VM.


Column Description

Memory Swap In

The amount of memory swapped in to the VMFS partition swap file for a VM.

Memory Swap Out

The amount of memory swapped out to the VMFS partition swap file for a VM.

Swapped Memory

The amount of memory swapped into and out of the VMFS partition swap file for a VM.

VMware Disk ReportUse this report to view disk statistics for the VMs (identified by display name) as shown in the following figure.

Analyze VMware Disk Report

The following table describes each of the columns in the report. You might need to scroll to the right to see some of the report columns.

Column Description

VMware Console Name



Column Description

Display Name

This value is used to refer to the VM. Each VM is identified by its display name specified in the VMware configuration file. This display name is not guaranteed to be unique on the VMware server. BMC Performance Assurance does not support duplicate VM display names within a VMware server. Virtual machines with the same display name are treated as one.

Disk Name

The host target logical unit number (LUN) for the disk.

Disk Shares

The number of disk shares assigned to a VM on the target device specified by the host target LUN.

Disk Reads

The number of disk reads (per second) for a VM on the target device specified by the host target LUN.

Disk Read in KB

The amount of data read (per second) for a VM on the target device specified by the host target LUN.

Disk Writes

The number of disk writes (per second) for a VM on the target device specified by the host target LUN.

Disk Writes in KB

The amount of data written in KB (per second) for a VM on the target device specified by the host target LUN.

VMware Storage Architecture


VMware Per Processor ReportUse this report to view CPU utilization information (per processor) for the system, as shown in the following figure.

Analyze VMware Per Processor Report


The following table describes each of the columns in the report:Column Description

VMware Console Name

The name of the VMware service console that provides all of the management functionality for the virtual machines. The service console OS in the VMware ESX Server is based on Red Hat version 7.2. The service console runs as another guest OS but has access to the VMware kernel to perform management functions.

CPU Number

Each virtual machine on the system is identified by a number.

CPU Util

The percentage of CPU time used by the physical computer, broken down by processor.

CPU Idle Time

The percentage of time the CPU is idle.


1. 2.

3.

4.

Viewing HP IVM data in AnalyzeAnalyze can be utilized to view detailed analytical data for HP IVM partitions. Some of the noteworthy capabilities of Analyze are:

Shows the total number of processors accessed per nPar or per nPar/vPar (100% = 1 processor).Uses the information available in the IVM configuration metric group to connect the host to the virtual machines.Uses the PID information in the IVM configuration group to retrieve the process record corresponding to the virtual machine.The resource usage reported for the process is used to compute the resource usage for each of the virtual machines.At this time, only CPU and memory numbers are available at each VM level.

Workload and Predict model characterization in AnalyzeIn addition to creating workloads by user definition or project, you can now create workloads for individual partitions (Integrity VM guests). The following types of workload characterization are supported for HP Integrity VM:

Build Workload By PartitionAnalyze automatically builds a workload for each Integrity VM partition.Partition Name is used as the workload name.The single process that represents the Integrity VM partition is assigned to the transaction or workload.Other non-partition processes are assigned to user-defined workloads.

User DefinedPartition-specific workloads are not created; only user-defined workloads are created.Works exactly the same as workload characterizations for standard systems.A user-defined workload is automatically renamed if there is a conflict with a workload built by partition.

To select the workload characterization type

In Analyze, create a new workload characterization or open an existing one.Select the workload characterization and from the menu, select . The Action PropertiesProperties dialog box for the selected workload characterization opens.On the General tab, click . The Advanced General Properties dialog Advanced Propertiesbox opens.Select the desired workload characterization type from the list.Build workload by

Analyze - Build workload by Partition option


Predict model

The HP Integrity VM host is represented as a computer or node object. When you select Build , the partitions are represented as workloads. The modeling functionality is Workload by Partition

similar to the functionality available for other platforms. Analyze creates a model that contains the host information along with all the workloads that are created for the host. The host looks like a regular host, and the virtual machine details are written to the model.

By default, an Analyze report shows one transaction per partition:

Analyze - Default option


1. 2. 3. 4.

5.

Viewing results for a Xen system in AnalyzeAnalyze has one report that presents information specific to Xen. To view the report, you must create a workload characterization file that includes the Xen node. An Analyze workload characterization contains parameters for doing the following:

Creating a performance model for use by PredictViewing charts of performance dataCreating performance reports

When you run Analyze, it uses the workload characterization to evaluate collected performance data, and create a performance model, reports, and, optionally, Visualizer input files.

To generate the Xen Summary report, perform the following steps:

Right-click in the Tree view, and select .Analyze Open Workload CharacterizationSelect the appropriate workload characterization ( ) file for the Xen system..anReview the displayed interval or set another interval.Run Analyze by clicking on the green arrow in the menu bar, or right-click the Workload Characterization in the Tree view and select .Start AnalyzeExpand the Reports item and then expand the Xen selection.

Analyze Xen Summary


5.

The following table describes each of the columns in the report. In the Analyze interface, you might need to scroll to the right to see some of the report columns.


5.

Column Description

Xen Host The name of the Xen node that provides all of the management functions for the Xen domains. For reporting purposes, this name is used to refer to the physical host computer.

Partition This value is used to refer to the Xen domain. Each domain is identified by its display name specified in the Xen configuration file.

Guest OS The operating system type installed as a guest OS on the VM. Each VM can run Microsoft Windows or Linux as guest OSs.

Physical Processors

The number of physical processors on the Xen server system. This value is shown only for the top-level server information.

Logical Processors

The number of logical processors on the Xen server system. This value is shown only for the top-level server information.

Virtual Processors

The number of CPUs allocated to the Xen domain. This value is shown for each Xen domain.

CPU Util The percentage of CPU time used by a Xen domain. The CPU usage shown in this column is a physical value; it represents the total CPU usage of the amount of CPU that has been allocated for the Xen domain.

CPU Shares

The number of CPU shares assigned to a Xen domain.

CPU Min The guaranteed minimum CPU percentage reserved for this Xen domain.

CPU Max The maximum CPU percentage for a Xen domain. The valid range of values is from zero ("0") to the number representing the total physical CPU resources. The maximum can be greater than 100 for SMP virtual machines that canuse more than one full physical CPU.

Total Memory

The amount of RAM (in MB) for the physical computer. This value is shown only for the top-level Xen node service console row.

Partition Memory Configured

The memory required for single copy of memory shared between Xen domains.

Memory Utilization

The sum of all memory used for running Xen domains.

Xen Type Specifies the type.

Types of Analyze workloads when using a Windows Gateway ServerA is a logical unit of work that represents a stream of related transactions, such as a workloadgroup of transactions for sales order entries, running on any of the following:

A single partitionA group of partitionsA single computerA network of computers


Predictor calculates the response time for each transaction in the workload. It also calculates throughput based on user input. You can control the number and types of workloads in your model, aggregating activities as needed through workload characterization in Analyze.

In terms of planning, it is useful to know whether you will create workloads for the purpose of reporting or for modeling. If you want to view collected data to see how specific systems are utilizing resources, creating workloads for reporting will suffice. If you want to see how these same systems might perform in scenarios, then you would create workloads for the purpose of What if...?creating models.

In general, workload types are defined by you but could include workloads for the purpose of:

ReportingModelingSeparating systems based on user type, such as sales, accounting, and so on

Additionally, there are predefined workloads. Predefined workloads are a set of customized workloads designed and supplied specifically for the Windows environment. These workloads characterize resource usage by the Windows operating system and by some typical Windows applications. These predefined workloads are defined as follows:

Predefined Analyze workloads for Windows systems

Workload Description

MS-APPS

This predefined workload contains all processes associated with the Microsoft Office suite of applications.

NT-INET This workload contains processes associated with Internet browsers such as Internet Explorer and Netscape Navigator.

NT-SCR-SAV

This workload contains processes associated with screen saver applications.

NT-SYS This predefined workload represents the Windows system and Windows network processes (such as rpcss.* and netdde.*). (These processes are not specific to network protocols such as NETBEUI, TCP, and so on.)

ZZZ A special workload that represents all processes that are not associated with any predefined, or user-defined, workload.

Windows console Analyze reports and what they meanThe following tables lists and describes the most useful reports Analyze produces with a Windows Gateway Server.

Useful Analyze reports and what they mean

Report Description


Run Summary Report

This report includes the Capture Ratio. The closer the Capture Ratio is to 1.0, the more effectively your workload characterization is modeling all work being done on your systems. The more the Capture Ratio differs from 1.0, the more you need to revise your workload characterization.

Process Aggregation

Process Detail

Both of these reports show important CPU consumers.

Process Tree Report

Shows how processes are related to each other; for example whether or not there are parent child relationships.

Transaction Utilization Report

Workload Composition

These reports let you assess workload and transaction definition effectiveness. For instance, are important CPU consumers where you want them to be? These reports also show whether there is too much in zzz.Analyze outputs from a Windows Gateway

ServerAnalyze outputs include the following files:

New or updated Analyze workload characterization files ( ).anModel files for Predictor ( ).mdReport files in ASCII, XML, or HTML formatVisualizer input files for Windows system data ( ).vis

The following table describes the files that are created during an Analyze run and stored in the Analyze output directory (by default .%BEST1_HOME%\local\workarea)

Output files created by an Analyze run

File Suffix

Description

*.html An Analyze report file in HTML format. Analyze uses this format to display its reports in the Gateway Server. You can also view the contents of these files, using a web browser such as Netscape Navigator or Internet Explorer 4.0 or later. Analyze stores its HTML report files in a directory with the name your-model-name_html.

*.xml An Analyze report file in XML format. Analyze uses XML to display its reports in the Gateway Server. You can also view the contents of these files, using a web browser such as Netscape Navigator or Internet Explorer 4.0 or later. Analyze stores its XML report files in a directory with the name your-model-name_xml.

*.ant An Analyze report file in ASCII text format.

*.md The model file to be used later by Predictor. This file contains all the information about hardware configuration, transactions, users, workloads and their resource consumption necessary to perform modeling with Predictor.

*.vis The Visualizer input files (optional Analyze output).

*.anlog

The message log from running Analyze (not viewable through the GUI).

*.anr. Analyze process information.

*.udrdbg

A log file which records any problems that might occur with reading data collected from repositories containing UDR file formats.


Using Analyze to do workload characterizationYour Manager script is already using a default workload characterization and creating a basic model of systems for you. However, for capacity planning, you want to create a workload characterization with workloads based on your systems' situations.

To do this, open Analyze and create a new workload characterization (also called a model specification) for Flounder, Salmon, and Minnow:

The creates a basic workload characterization and guides New Workload Characterization Wizardyou through adding computers to the characterization. Check that the console data repository is set correctly for each computer you add, so that Analyze can find the collected data.

You will need to select the interval of data to analyze and model. To do this open the Interval object under Analyze. The Interval function offers several ways of viewing data and selecting an interval of data to model. You can look at the Interval charts for CPU utilization and I/O rate. Additionally, you should review the charts for Paging Rate, CPU Queue Length, Disk Space Usage, and Memory Utilization, then proceed with analysis of your three systems.

To view CPU Utilization accept the default, CPU Utilization, from the list and click . In the Chartresulting chart, drag and click to select and enlarge the analysis interval. Analyze Interval offers several ways to select analysis intervals. You extend the interval to eight hours, for an overall system average as shown in the the following figures. Analyze automatically adjusts the analysis interval to available spills within a single collection.

Charting CPU utilization


Details of CPU utilization

Continue with .Characterizing the workload


Characterizing the workloadAfter you have defined an analysis interval, you need to characterize the workloads that you will be moving to Flounder. Workloads include both users and transactions. Because you plan to move all users from Minnow and Salmon, you can use the default user class in the workload. However, you are not moving all processes. For instance, Perform processes will remain. So, you must define

for the processes that will be moving and for the ones separate transaction classes and workloadsthat stay behind.

Right-click to start the . When you specify Transactions Independent Transactions Wizardprocesses, Analyze lists all the processes in the interval of collected data that you are looking at, and you select from the list as shown in the following figure.

Selecting the process for the transaction

After completing this transaction class, open the again. You Independent Transaction Class Wizardneed to create another transaction class and select all processes the BMC processes. exceptWhen you finish, the new transaction classes show up in the scope pane as shown in the following figure.

Resulting transaction classes


1.

The next step is to create separate workloads. Use the to create the New Workload Wizardworkloads. For the workload of processes that are not moving, select the computers contributing to that workload: Flounder, Minnow, and Salmon. Select the transaction class that is staying, BMC, and the user class (none).

For the workload of processes that are going to be on Flounder, select the computers contributing to that workload: Flounder, Minnow, and Salmon, again. You select the transaction class for processes to be on Flounder, and you select the default User Class, .zzz

Because Analyze can evaluate a process only once when you analyze the workload characterization, you must set the precedence order of your workloads. To do this, right-click

and select . Set the precedence orders.Workload Classes Properties

Setting workload precedence

After you have created the separate transactions and workloads:

Save the Console settings.


2. Select your workload characterization, and click the green triangle in the command bar to run Analyze and create the model.

To check that the model is satisfactory, review key reports (see Windows console reports and what ). Checking reports is essential. You want to make sure that the model is they mean (see page 20)

adjusted to capture all CPU use and I/O. For example, by using the Workload Composition Report you can see what processes and users were added to the actual workload. This report is useful in verifying that the work was allocated according to your expectations. After viewing reports you determine that the model looks satisfactory, so you decide to use it for planning in Predict.

Continue with .Test-running changes with the model using a Windows Gateway Server

Administering AnalyzeFor information on administering Analyze, see:

Additional information about analysis intervals on a Windows Gateway Server (see page 26)Creating and using workload characterizations (see page 29)

Additional information about analysis intervals on a Windows Gateway ServerIn addition to the basic functionality described in Selecting an appropriate analysis interval with a

, you can browse data for a particular interval, or you can browse Windows console (see page 31)a summary of all collected data files available for the selected computers.

If you click on the interval results display (see ), you will see Chart Interval results (see page )the options shown in the following table.

Definitions of options in the Chart list

Field Name Definition

CPU Utilization Total

The percentage of total CPU capacity used during the interval.

CPU Util per CPU The percentage of CPU utilization per CPU.

I/O Rate The total number of I/O pages (in 4KB blocks) transferred for each computer and disk during the interval.

Memory The percentage of total memory capacity used during the interval.

Disk Usage The total disk utilization for each computer and disk during the interval.

Raw Paging Rate The disk paging rate, reported as pages per second.

CPU Queue Length The length of the queue of requests for CPU time.

All Charts Displays all graphs.

https://docs.bmc.com/docs/display/btcopdf/Test-running+changes+with+the+model+using+a+Windows+Gateway+Server


Field Name Definition

All Charts - Tiled Displays all graphs in a tiled arrangement.

CPU Utilization Total chart

In the chart format you can set guideline and threshold values to view the plotted graphs of statistics in relation to those values. The guideline value represents the point at which performance is unacceptable levels. The threshold value represents the point at which performance approachinghas or unacceptable levels.reached exceeded

Note

The CPU utilization field on this chart does not normalize the data by the number of processors in the computer, as is done in the interval results pane. For example, given the following scenario:A computer with four processors that has totaled 20 minutes of CPU time for all four processors during a 10-minute interval.In the interval results pane, the CPU utilization is reported as 50%, because each processor is using an average of five minutes per processor. However, in the chart, the CPU utilization is shown as 200%, which is the accumulated CPU utilization for all four processors in the computer.

While a chart is displayed, click to display the dialog box. Use this dialog Options Chart Optionsbox to set the guideline and threshold values for the various graphs that you can display.

You can save the chart as an HTML file for later display in your browser. To do this, right-click a chart while it is displayed, then select from the menu.Save as HTML



Restrictions on the analysis interval (see page )Criteria for interval selection (see page )

Restrictions on the analysis intervalYou should select an analysis interval that lies completely within an interval covered by collected data in which you are interested. If you do not, Analyze selects the best fit interval based on the following rules:

The interval will be the overlapping part of the analysis interval specified in the Start and End fields of the Analyze Interval pane and the total run interval of one of the collected data files available for a computer.The interval chosen will be the longest of all available choices.

The following limitations are consequences of the interval selection restrictions:

You cannot select disjoint intervals for the same model.You cannot combine more than one collected data file into a longer analysis interval, even if they overlap in time.

The smallest possible analysis interval is the spill interval specified for data collection. The default for the spill interval is 15 minutes. While the interval selection granularity is in minutes, Analyze rounds it off to the spill interval length. For example, if the spill interval is 15 minutes and you select an analysis interval of 20 minutes, Analyze will actually set the interval to 30 minutes.

Criteria for interval selectionSelecting an appropriate measurement interval is important to the success of any modeling study you undertake. The interval you select should be as representative as possible of the current workload on the system. To select a suitable interval, conduct a trend analysis, looking at the historical data covering a one- or two-week period. Look for the following:

Is the pattern of daily utilization of resources (CPU, disk I/O) consistent from day to day and from week to week?Do any peak periods of resource usage stand out? What are the periods with the greatest CPU utilization? Are there any periods during which workloads have become I/O bound?

Focus on peak intervals if you want to study intervals of one to two hours. The peak period is usually the interval that you should select for modeling, as the performance needs of users are most critical during such times. An analysis performed over time periods longer than one or two hours tends to smooth out utilizations and gives an averaged view that hides peaks and troughs.


But, perhaps you are interested in the average workload on the system, rather than peak utilizations. In this case the interval with the highest CPU (or other) utilizations would not be appropriate.

The job mix must also be taken into account. Batch jobs could have the same CPU utilization as interactive jobs, but with batch jobs, throughput will be the important issue, while response time is the relevant issue for interactive users.

You can find peak load times by looking at the information generated in the Analysis Interval window.

To ensure that you select the right data, give careful consideration to the following general guidelines. They will help you to define clearly your criteria for selecting an interval.

Look at the performance metrics of the intervals you are considering. These metrics include CPU Utilization, I/O rate, and Paging Rates. Examine the following questions:

Is there an unusually high amount of activity when you would expect little?Are there consistent patterns of high utilization?Are some computers more active than others?Can you correlate the performance metrics with any known performance problems?Are there known periods of high demand?

Limit your interval to the period of low variability of performance parameters. For instance, if a period of very high utilization and a period of low utilization are right next to each other, do not try to analyze them both in one model. You will obtain averaged results that are not directly applicable to either period. Create separate models to analyze intervals with significantly different characteristics.

For more information, see .Creating workloads for modeling use in Predict (see page )

Creating workloads for modeling use in PredictWhenever you crate a workload characterization file and run Analyze, a model file is automatically created for use in the Predict component of BMC Performance Assurance. Even though the creation of this file is automatic, other considerations need to be taken into account if you are going to use collected data for modeling. The computers that are selected, the time of data collection, and the intervals selected might be different for an analysis created for modeling purposes, rather than for the purpose of viewing reports. See Modeling techniques using a Windows Gateway Serverfor more information about these considerations.

Creating and using workload characterizationsFor information about creating and using workload characterizations with a Windows Gateway Server, see:

Creating a standard workload characterization file (see page 30)


1. 2.

3.

4.

5.

Selecting an appropriate analysis interval with a Windows console (see page 31)Analyzing the collected data using a Windows console (see page 33)Viewing Analyze reports using a Windows console (see page 34)Using the Analyze cut-disk option on a Windows Gateway Server (see page 41)

Creating a standard workload characterization fileThis example uses the defaults provided by the Analyze component to demonstrate what should be considered in creating a workload.

To create a workload characterization file

Right-click the Analyze snap-in, then select .New Workload CharacterizationWhen the welcome dialog box of the Analyze Workload Characterization Wizard opens, click .NextIn the dialog box, assign a name for your workload Workload Characterizationcharacterization file, then click . In this example, the file is named .Next Default_wkldIn the dialog box, select the appropriate check boxes (default settings Analyze Propertiesare shown in the figure below).Click .Finish

This launches the New Computer wizard. Use this wizard to define the computers that are to be included in the Analyze workload characterization file. These computers will be represented in the Analyze reports and the performance model that Analyze builds.

Default Analyze workload properties


For more information about using the default workload characterization, see:

Selecting an appropriate analysis interval using a Windows Gateway Server (see page ).Analyzing the collected data using a Windows Gateway Server (see page ).Windows console Analyze reports and what they mean (see page 20).

Selecting an appropriate analysis interval with a Windows consoleThe data used in this example was collected over a one-hour period. In practice, you might have collected data a number of times, with each run covering a period of many hours. It is unlikely that you would want or need to run Analyze against such a large amount of data.

A more manageable approach is to focus on analyzing the period that is most relevant to your goals. Such a period is usually no longer than a few hours. In this case, we will select an interval that encompasses the time period we want to study.

The Interval results pane (see figure below) shows all of the collected data available for the computers used in this example. You can use the results pane to select individual computers and browse through the data.


1.

2.

Note

Data is only available if the computers on which the data was collected have application instances installed. If no data is available, a message appears stating that no application data is available.

Interval results

To select an analysis interval

In the scope pane, expand one of the workloads on the tree and select the Interval object. This displays the analysis data for the computers in the workload (see the figure above).Click a tab to select the type of data to use. In this example, data is chosen.System


3.

4.

5.

Expand each computer in the interval results pane and further expand the intervals to show the sub-intervals (see the following figure).Sub-intervals

While holding down the key, select the intervals. In this example, the second interval of Ctrleach computer is chosen.Click to set the Analyze interval to the selected intervals (see the circled area in the Setabove figure). The data will include all the data collected during the four sub-intervals selected.

The interval results data appears in text format. For a chart of any text field, select a chart in the list. For more information about working with Analyze intervals, see Additional information about

.analysis intervals on a Windows Gateway Server (see page 26)

Analyzing the collected data using a Windows consoleAt this point we have created an Analyze workload characterization file ( ) and Default_wkld.anselected an interval to study. This information can be used for creating reports to view in Analyze or to create a model file for use in Predict. The next step is to run Analyze against the selected data to build a model file and create a set of Analyze reports.


To run Analyze

Right-click the workload characterization file and select .Start AnalyzeWhile processing data and creating output files, Analyze displays a progress message. When Analyze completes the analysis, the progress message disappears. At that point, the reports created by Analyze can be viewed.

Viewing Analyze reports using a Windows consoleAfter you have analyzed the collected data and built a model, you can view the output data through a variety of reports. These reports provide a summary of network, computer, memory, and other activity for the analysis interval.

For more information about viewing reports, see:

Run Summary report (see page )Looking at important CPU consumers (see page )Process Tree report (see page )Transaction Utilization and Workload Composition reports (see page )Exporting data in XML format using a Windows Gateway Server (see page )Generating HTML reports using a Windows Gateway Server (see page )

Analyze Run Summary reportThe Analyze Run Summary report includes the capture ratio (see figure below). In this example, the capture ratio is 1.0, indicating that, for this computer, the workload is effectively modeling the work being done on the system. A look at the capture ratios for the other computers (not shown) shows that they fall within acceptable ranges also.

Analyze Run Summary report


Looking at important CPU consumersThe Process Aggregation and the Process Detail Analyze reports provide information about important CPU consumers (see the following figures).

Analyze Process Aggregation report


Analyze Process Detail report


Analyze Windows Process Tree reportThe Analyze Windows Process Tree report shows how Windows processes are related to each other and indicates any parent-child relationships (see figure below). The circled area shows parent-child relationships for some of the processes in one computer in the workload.

Analyze Windows Process Tree report


Transaction Utilization and Workload Composition Analyze reportsThese Analyze reports let you assess workload and transaction definition effectiveness. They also show whether there is too much in zzz. In the following figures, zzz is too high, indicating that the default workload characterization is not appropriate for the data. If this data was to be used for reporting or modeling, the workloads would need to be altered before it would be effective.

Analyze Transaction Utilization report


Analyze Workload Composition report


1. 2. 3. 4.

Exporting data in XML format using a Windows Gateway ServerWhenever you run Analyze, an XML file is created in the folder. %BEST1_HOME%\local\workareaThis XML file is same as the name of the workload characterization file with appended to the .xmlname. You can specify options in Analyze that allow you to export BMC Performance Assurance data to an XML file in a location that you specify. You can then use third-party products to further analyze the data and create additional reports. To do so, complete the following steps:

Right-click the workload characterization file and select .PropertiesClick .Advanced PropertiesWhen the dialog box opens, select .Advanced General Properties Generate data for exportSpecify the location for the XML file, or click to navigate to a location (see figure Browsebelow).


5.

1. 2.

3.

Save the workload characterization file and run Analyze again to see the data in this location.Exporting data

Generating HTML reports using a Windows Gateway ServerYou can also create HTML reports. To do so:

Right-click the workload characterization file and select .PropertiesClick the tab and click the box next to . This will Analyze Output Generate HTML report filesturn on the generation of reports..htmlRun Analyze again to generate the HTML files.These HTML reports will be placed in a sub-folder under %BEST1_COLLECT_HOME%

. The name of the sub-folder is the same as the name of the workload \local\workareacharacterization file with appended to the name. For example, HTML reports for the .html

file are located in Default_wkld.an %BEST1_COLLECT_HOME%\local\workarea\Default_wkld.html.

Using the Analyze cut-disk option on a Windows Gateway ServerThe cut-disk option reduces the size and complexity of BMC Performance Assurance models by cutting individual disks and logical volumes that have little or no measured I/O activity. The I/O activity of the disks and logical volumes from the model is represented by Analyze as a single cutdisk and logical volume. The benefits of this consolidation are:

Reduced number of insignificant disks that you need to visualizeImproved overall performance of reading models generated by Analyze


The consolidated disk has no real physical significance in your Windows environment, but it does contain all of the resources (I/O, service time, and size) that are used by the disks eliminated from the model. When working with the model in Predictor, the consolidated disk is treated as a delay disk rather than a queuing disk. In this case, Predictor uses the service time directly for the response time or to calculate the response time. This treatment prevents the response time of transactions requesting service from this disk from competing for resources that would otherwise be distributed across many disks. As a result, the response time of transactions requesting service from this disk will contain no wait time and will consist only of the service time.


Rules of operation for the cut-disk option using a Windows Gateway Server (see page )Case study of the effects of the cut-disk command using a Windows Gateway Server (see page )

Rules of operation for the cut-disk option on a Windows Gateway ServerBy default, the cut-disk option is inactive. You must specify – in either Analyze or Manager – that you want to use the cut-disk command to reduce the size of the model related to the I/O subsystem.

You can specify the name of the consolidated disk containing the cut disks as well as the disk model. The default name and model of the consolidated disk are and GENERIC-DISK.zzzcutdisk

To control which physical disks are cut from the model, you specify the minimum value for either disk utilization percentage or I/O rate in pages per second. For example, suppose you want to cut any disk in the model with disk utilization less than or equal to 10%. The setting as it would be entered in Analyze appears in the following figure.

Analyze cut-disk option


Any disk, or disk storage array, including RAID, can be cut except for disks that contain paging logical volumes. After a disk storage array is cut, it is treated as a normal disk.

The resources of the disks cut by the cut-disk command are accumulated for the consolidated disk. The only resources not accumulated are the disk active time and disk utilization.

Analyze and Predictor reports will present only the resources used by the consolidated disk and any other physical disk not eliminated by the cut-disk command.

Analyze provides additional information in the report, which shows the detailed .anrfile nameactivity of the disks eliminated by the cut-disk command. Analyze also writes informational messages to the file to indicate which disks were cut..anlogfile name

Case study of the effects of the cut-disk command on a Windows Gateway ServerIn this case study, our goal is to reduce the number of physical disks on a computer named gremlin. To accomplish this, we specify a cut-disk command for disk utilization less than or equal to 10%. (The figures below show the effects of the cut-disk command.) As a result of applying this cut-disk command, Analyze:

Cut disks sd2 and sd3 and assigned their I/O activity to the consolidated disk zzzcutdisk.Created a single logical volume (zzzlv@zzzcutdisk) and disk controller (zzzdc) to support the new consolidated disk.


Excluded disk sd1 because it contains a paging volume.Excluded disk sd0 because it has 11.5% utilization and contains a paging logical volume.

The tables below show disk and logical volume statistics before and after using the cut-disk command.

Physical disk configuration before applying cut-disk (Windows)

Physical disk configuration after applying cut-disk (Windows)

Disk statistics before applying cut-disk (Windows)

Disk Controller Utilization (%) Total I/O Rate (pages/sec) Page Rate (pages/sec) Service Time (ms/page)

sd0 isp0 11.5 9.2 3.5 12.5



sd1 isp1 3.2 2.9 2.9 11

sd2 isp2 7.5 5.2 0 14.4

sd3 isp3 1.5 4.3 0 3.5

Logical volume statistics before applying cut-disk (Windows)

Disk Logical Volume Type Total I/O Rate (pages/sec)

sd0 9.2

zzzlv@sd0 General 5.7

vg00_lvo11 Paging 3.5

sd1 2.9

zzzlv@sd1 General 0


sd2 5.2


sd3 4.3


Disk statistics after applying cut-disk (Windows)


sd0 isp0 11.5 9.2 3.5 12.5

sd1 isp1 3.2 2.9 2.9 11

zzzcutdisk zzzdc 7.5 10.0 0 7.9

Logical volume statistics after applying cut-disk (Windows)

Disk Logical Volume Type Total I/O Rate (pages/sec)

sd0 9.2



sd1 2.9

zzzlv@sd1 General 0


zzzcutdisk 10.0

zzzlv@zzzcutdisk General 10.0


Index

aanalyze , , , , , , , , , , , , , , , , , , 3 5 6 7 8 10 11 13 15 15 17 19 20 21 28 28 30 31

, , , , , , , 33 34 35 37 38 41 42 43

bbmc performance assurance , , , , , , , , 6 7 8 10 11 13 15 15 17bmc performance assurance console , , , , , , , , , , , , 3 3 5 6 19 20 21 22 24 26 28 28

, , , , , , , , , , , , 29 30 31 33 34 34 35 37 38 40 41 42 43

cconsolidating servers , 22 24cut disk , 42 43

hhp ivm , 15 15html reports 41

iintervals , , , 26 28 28 31

mmodeling , , 22 24 29

ooracle 6


ppartitions 6performance 6

rreports , , , , , , , , , 8 10 11 13 20 34 34 35 37 38

uuse cases 29using , , , , , , , , , , , , , , , , , , 3 3 5 6 6 7 8 10 11 13 15 15 17 19 21 22 24 26

, , , , , , , , , 28 28 30 33 34 35 37 38 40 42

vviewing results , , , , 7 8 10 11 13vmware , , , , 7 8 10 11 13

wwindows , , , , , , , , , , , , , , , , , 3 5 6 19 20 21 22 24 26 28 28 29 30 31 33 34 34 35, , , , , , 37 38 40 41 42 43workloads , , , , , , 3 3 5 19 24 29 30

xxen 17xml export 40


© Copyright 2013 - 2016 BMC Software, Inc.

© Copyright 2013 - 2016 BMC BladeLogic, Inc.

BMC, BMC Software, and the BMC Software logo and the BMC marks listed at are the exclusive bmc.com/legal/trademarksproperties of BMC Software, Inc., or its affiliates or subsidiaries and are registered or are pending registration with the U.S. Patent and Trademark Office and/or in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

BladeLogic and the BladeLogic logo are the exclusive properties of BladeLogic, Inc. The BladeLogic trademark is registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BladeLogic trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

IBM, AIX, WPAR, LPAR, DLPAR, SPLPAR, PowerVM, POWER5, POWER6, and POWER7 are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

IT Infrastructure Library® is a registered trade mark of AXELOS Limited.

ITIL® is a registered trade mark of AXELOS Limited.

Linux is the registered trademark of Linus Torvalds.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

UNIX® is the registered trademark of The Open Group in the US and other countries.

BMC Software Confidential. BladeLogic Confidential.

The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation.

Click for the provisions described in the BMC License Agreement and Order related to third party products or technologies hereincluded in the BMC product.

BMC Software Inc.2103 City West Blvd, Houston TX 77042-2828, USA713 918 8800Customer Support: 800 537 1813 (United States and Canada) or contact your local support center

http://www.bmc.com/legal/trademarks/

Documents

BMC TrueSight Capacity Optimization - Analyze€¦ · Analyze processes operating system and applications data from multiple systems and creates a multiple workload representation