| In the upcoming sections we'll run some commands associated with performance analysis to see how the output of these differ from the output you would see on a non-vPars system. Since the commands we're going to cover are the basis for much performance analysis-related work, it is important to know what differences you'll see in the output of these commands. The non-vPars-specific part of this chapter covers performance analysis in general. Performance analysis on a vPar is performed in the same manner as performance analysis on a non-vPar system except that the output of some commands will not display all of the components on your system. Instead, only the components devoted to the vPar on which you're performing analysis will be displayed and analyzed. This is the area we'll focus on in the first part of this chapter, the output you'll see for some commonly used commands. On a purely performance-related note, you do indeed have additional software running on your system with vPars, the Virtual Partition Monitor. Some of the resources on a vPars system are shared, in the sense that they're owned by the Virtual Partition Monitor rather than an individual vPar such as System Bus Adapters and the Memory Controller. The Virtual Partition software consumes a minimal amount of overall system resources. The com-ponents in a vPar are devoted exclusively to the operation of the vPar to which they are assigned. This means that when we run a performance analysis on a vPar, we are analyzing only the components devoted to the vPar. Let's take a look at some commonly used performance analysis commands in the upcoming sections and see what the vPars outputs look like. This is by no means an exhaustive list of commands, but it will give you an idea of what you'll see with vPars. |