HP-UX Virtual Partitions

   

HP-UX Virtual Partitions

By Marty Poniatowski

Table of Contents
Chapter 11.  System Administration Manager (SAM)

Under Performance Monitors, you can view the performance of your system in several different areas such as disk and virtual memory. Figure 11-41 shows the menu hierarchy of Performance Monitors:

Figure 11-41. Performance Monitors Menu Structure

Performance Monitors provides you with a window into several areas of your system. If you are serious about becoming familiar with the tools avail-able on your system to help you understand how your system resources are being used, you should take a close look at Chapter 12. Chapter 12 is devoted to getting a handle on how your system resources are being used, including many built-in HP-UX commands. Some of the performance monitors you can select in this subarea are HP-UX commands, which you'll need some background in before you can use them. I'll cover these areas only briefly because this material will be covered in more detail in Chapter 12.

Disk and Terminal Activity

Selecting Disk and Terminal Activity opens a window that shows the output of iostat -t. I have included the description of iostat from Chapter 12 to save you the trouble of flipping ahead. When the Disks and Terminal Activity window with the output of iostat is opened for you, it shows a single iostat output. When you press Return, the window is automatically closed for you.

The iostat command gives you an indication of the level of effort the CPU is putting into I/O and the amount of I/O taking place among your disks and terminals. The following example shows the iostat -t command, which will be executed every three seconds, and associated output from an HP-UX 11.x system:

# iostat -t 3 tty cpu tin tout us ni sy id 78 42 2 0 28 70 /dev/dsk/c0t1d0 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0 bps sps msps bps sps msps bps sps msps 0 0 0 33 8.3 25.2 7 1 19.5 tty cpu tin tout us ni sy id 66 24 0 0 30 70 /dev/dsk/c0t1d0 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0 bps sps msps bps sps msps bps sps msps 5 12 15.9 36 9.7 21 7 1.2 13.8 tty cpu tin tout us ni sy id 90 29 1 0 25 73 /dev/dsk/c0t1d0 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0 bps sps msps bps sps msps bps sps msps 12 1.7 15.5 24 3 19.1 14 2.1 14.6 tty cpu tin tout us ni sy id 48 16 1 0 16 83 /dev/dsk/c0t1d0 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0 bps sps msps bps sps msps bps sps msps 0 0 0 62 9.3 18 12 2 17.2 tty cpu tin tout us ni sy id 32 48 7 0 14 79 /dev/dsk/c0t1d0 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0 bps sps msps bps sps msps bps sps msps 1 0.3 14.4 5 .9 16.2 171 29.4 18.2 tty cpu tin tout us ni sy id 2 40 20 1 42 27 /dev/dsk/c0t1d0 /dev/dsk/c0t4d0 /dev/dsk/c0t6d0 bps sps msps bps sps msps bps sps msps 248 30.9 20.8 203 29.2 18.8 165 30.6 22.1

Descriptions of the reports you receive with iostat for terminals, the CPU, and mounted file systems follow.

For every terminal you have connected (tty), you see a "tin" and "tout," which represent the number of characters read from your terminal and the number of characters written to your terminal, respectively. The -t option produces this terminal report.

For your CPU, you see the percentage of time spent in user mode ("us"), the percentage of time spent running user processes at a low priority called nice ("ni"), the percentage of time spent in system mode ("sy"), and the percentage of time the CPU is idle ("id").

For every locally mounted file system, you receive information on the kilobytes transferred per second ("bps"), number of seeks per second ("sps"), and number of milliseconds per average seek ("msps"). For disks that are NFS-mounted or disks on client nodes of your server, you will not receive a report; iostat reports only on locally mounted file systems.

GlancePlus

GlancePlus is available here if it is installed on your system. You are given the choice of using either the Motif (graphical) version or the character mode version of GlancePlus. GlancePlus and other HP VantagePoint products are covered in Chapter 12.

Inter-Process Communication Facility Status

Inter-Process Communication Facility Status shows categories of information related to communication between processes. You receive status on Message Queues, Shared Memory, and Semaphores. This is a status window only, so again, when you press Return, and the window closes.

Processes with Highest CPU Usage

Processes with Highest CPU Usage is a useful window that lists the processes consuming the most CPU on your system. Such useful information as the Process ID, its Resident Set Size, and the Percentage of CPU it is consuming are listed.

System Activity

System Activity provides a report of CPU utilization. You receive the following list:

%usr

Percent of CPU spent in user mode.

%sys

Percent of CPU spent in system mode.

%wio

Percent of CPU idle with some processes waiting for I/O, such as virtual memory pages moving in or moving out.

%idle

Percent of CPU completely idle.

System Properties

System Properties gives you a great overview of system specifics. Included here are those hard-to-find items such as processor information, CPU version, clock frequency, kernel support (32-bit or 64-bit), memory information, operating system version, and network IP and MAC addresses.

Virtual Memory Activity

Virtual Memory Activity runs the vmstat command. This too is covered in Chapter 12, but I have included the vmstat description here so that you don't have to flip ahead. Some of the columns of vmstat are moved around a little when the Virtual Memory Activity window is opened for you.

vmstat provides virtual memory statistics. It provides information on the status of processes, virtual memory, paging activity, faults, and a breakdown of the percentage of CPU time. In the following example, the output was produced ten times at five-second intervals. The first argument to the vmstat command is the interval; the second is the number of times you would like output produced.

# vmstat 5 10:

procs

 

memory

   

page

   

faults

 

cpu

 

r

b

w

avm

free

re

at

pi

po

fr

de

sr

in

sy

cs

us

sy

id

4

0

0

1161

2282

6

22

48

0

0

0

0

429

289

65

44

18

38

9

0

0

1161

1422

4

30

59

0

0

0

0

654

264

181

18

20

62

6

0

0

1409

1247

2

19

37

0

0

0

0

505

316

130

47

10

43

# vmstat 5 10:

procs

 

memory

   

page

   

faults

 

cpu

 

r

b

w

avm

free

re

at

pi

po

fr

de

sr

in

sy

cs

us

sy

id

1

0

0

1409

1119

1

10

19

0

0

0

0

508

254

180

69

15

16

2

0

0

1878

786

0

1

6

0

0

0

0

729

294

217

75

17

8

2

0

0

1878

725

0

0

3

0

0

0

0

561

688

435

67

32

1

2

0

0

2166

98

0

0

20

0

0

0

66

728

952

145

8

14

78

1

0

0

2310

90

0

0

20

0

0

0

171

809

571

159

16

21

63

1

0

0

2310

190

0

0

8

1

3

0

335

704

499

176

66

14

20

1

0

0

2316

311

0

0

3

1

5

0

376

607

945

222

4

11

85

You will get more out of the vmstat command than you want. Next is a brief description of the categories of information produced by vmstat:

Processes are classified into one of three categories: runnable ("r"), blocked on I/O or short-term resources ("b"), or swapped ("w").

Next you will see information about memory. "avm" is the number of virtual memory pages owned by processes that have run within the last 20 seconds. If this number is roughly the size of physical memory minus your kernel, then you are near paging. The "free" column indicates the number of pages on the system's free list. It doesn't mean that the process has finished running and these pages won't be accessed again; it just means that they have not been accessed recently.

Next is paging activity. The first field (re) shows the pages that were reclaimed. These pages made it to the free list but were later referenced and had to be salvaged. Check to see that "re" is a low number. If you are reclaiming pages that were thought to be free by the system, then you are wasting valuable time salvaging these. Reclaiming pages is also a symptom that you are short on memory.

Next you see the number of faults in three categories: interrupts per second, which usually come from hardware ("in"); system calls per second ("sy"); and context switches per second ("cs").

The final output is CPU usage percentage for user ("us"), system ("sy"), and idle ("id"). This is not as complete as the iostat output, which also shows nice entries.


       
    Top
     

    Категории