You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

\n \n \n \n \n \n \n \n \n \n \n \n \n
Related DocumentationVersion of up.time \naffectedAffected Platforms
\nAllIRIX
\n \n

The up.time IRIX agent collects the following performance metrics from the systems on which it is installed:

\n \n \n \n

The IRIX agent uses a number of utilities to gather these metrics including:

\n \n
    \n
  • sar: collects information about system activity.
    • \n
  • ifconfig: configures the parameters for network interfaces.
    • \n
  • ps: reports on the status of processes.
    • \n
  • netstat: reports on network status.
    • \n
\n \n

Each set of performance metrics is averaged between the interval at which the up.time monitoring station polls the agent (e.g. every 10 minutes).

\n \n

CPU

\n \n

The up.time agent uses the sar utility (with the -u and -f options) to collect the metrics listed below from an IRIX system. The statistics returned by the agent are averaged for all CPUs on the system.

\n \n
\n \n\t \n\t \n \n \n\t \n \n\t \n \n \n \n\t \n \n\t \n \n \n \n\t \n \n\t \n \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n
MetricExplanation
% UsrThe amount of time that the CPU spends in user mode.
% SysThe amount of time that the kernel spends processing system calls.
% WIOThe amount of waiting time that a runnable process for a device takes to perform an I/O operation.
Multi CPU UsageWhether or not a system wity multiple CPUs is effectively balancing tasks between CPUs, or if processes are being forced off CPUs in certain circumstances.
Run Queue LengthThe percentage of time that one or more services or processes are waiting to be served by the CPU.
Run Queue OccupancyThe percentage of time that one or more services or processes are waiting to be served by the CPU.
\n \n

Multi-CPU

\n \n

The up.time agent collects the metrics listed below from IRIX systems with multiple CPUs. The CPU statistics output by the agent are an average of all the CPUs on the server.

\n \n
\n \n\t \n\t \n \n \n\t \n \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n
MetricExplanation
User % The percentage of CPU user processes that are in use.
System %The percentage of CPU kernel processes that are in use.
Wait I/O %The percentage of time that a process which can be run must wait for a device to perform an I/O operation.
SMTX The number of read or write locks that a thread was not able to acquire on the first attempt, as reported by the mpstat command.
XCALThe number of interprocess cross-calls. In a multi-processor environment, one processor sends cross-calls to another processor to get that processor to do work. Cross-calls can also be used to ensure consistency in virtual memory. Heavy file system activity such as NFS can result in a high number of cross-calls.
InterruptsThe number of CPU interrupts.
Total %The total amount of User %, System %, and Wait I/O%.
\n \n \n

Memory

\n \n

The up.time agent uses the sar utility with the following options to collect memory metrics from an IRIX system:

\n \n
    \n
  • -w -f (swap activity)
    • \n
  • -b -f (buffer activity)
    • \n
  • -p -f (paging activity)
    • \n
\n \n

The statistics the agent returns are for the entire system.

\n \n
\n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n \n\t \n \n \n
MetricExplanation
Free MemoryThe amount of physical memory available to the operating system, system library files, and applications.
Cache Hit RateHow often the system accesses the CPU cache.
Page-outs/sThe rate at which pages were written to disk.
Page-ins/sThe rate at which pages were read from or written to the disk.
Page Frees/sThe number of pages that are freed from memory each second.
Attaches/sThe number of pages that get attached to memory each second.
Page-out Requests/sThe number of requests to perform a write operation that occur each second.
Page-in reqs/sThe number of requests to perform a read operation that occur each second.
PageScans/sThe number of pages that are scanned each second.
PageFaults/sThe number of page faults that occur each second.
Software Locks/sThe number of software locks that are issued each second.
\n \n

Disk

\n \n

The up.time agent uses the sar utility with the -d and -f options to collect the disk metrics listed below from an IRIX system. The agent collects volume capacity statistics from each filesystem, while the disk statistics (%busy, Read/Write/s) returned are for each disk.

\n \n
\n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n
MetricExplanation
Disk (Spindle) NameThe names of each disk on the system.
Usage (% Busy)The percentage of time during which the disk drive is handling read or write requests.
Blocks per secondThe number of read and write operations on the disk that occur each second.
Transfers/sThe average number of bytes that have been transferred to or from the disk during write or read operations.
Average Queued RequestsThe number of threads that are waiting for processor time.
Average Service TimeThe average amount of time, in milliseconds, that is required for a request to be carried out.
Average Wait TimeThe average time, in milliseconds, that a transaction is waiting in a queue. The wait time is directly proportional to the length of the queue.
\n \n

Network

\n \n

The up.time agent uses the following utilities to collect network data from an IRIX system:

\n \n
    \n
  • ifconfig -a
    • \n
  • netstat -s
    • \n
\n \n

Except for TCP retransmits, the agent averages all statistics per interface.

\n \n
\n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n
MetricExplanation
Receive RateThe rate, in kilobytes per seconds, at which data is received over a specific network adapter.
Send RateThe rate, in kilobytes per seconds, at which data is sent over a specific network adapter.
Packets Inbound ErrorsThe number of inbound packets that contained errors, which preventing those packets from being delivered to a higher-layer protocol.
Packets Outbound ErrorsThe number of outbound packets that could not be transmitted because of errors.
CollisionsThe number of signals from two separate nodes on the network that have collided.
TCP RetransmitsThe number of packets that have been re-sent over a network interface.
\n \n

Process

\n \n

The up.time agent uses the ps utility with the -ef option to collect the process data listed below from an IRIX system. By default, the agent only gathers the top 20 processes, and sorts them by the highest CPU usage.

\n \n
\n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n \n\t \n\t \n \n \n\t \n\t \n
MetricExplanation
Number of ProcessesThe number of processes that are currently running on a system.
Process Creation RateThis metric determines whether or not there are runaway processes on a system or if a forking-based process (like a Web server) is spawning too many processes over a specified period of time.
Processes RunningThe number of processes that are currently running.
Processes BlockedThe number of processes that are currently being blocked from running.
Processes WaitingThe number of processes that are currently waiting to runn.
Workload - UserThe demand that network and local services are putting on the system, based on the IDs of the users who are logged into a system.
Workload - GroupThe demand that network and local services are putting on the system, based on the IDs of the user groups that are logged into a system.
Workload - Process NameThe demand that network and local services are putting on a system, based on the processes that are running.
Workload Top 10 - UserThe 10 network and local services that are are putting the most load on the system, based on the IDs of the users who are logged into a system.
Workload Top 10 - GroupThe 10 network and local services that are are putting the most load on the system, based on the IDs of the user groups who are logged into a system.
Workload Top 10 - Process NameThe 10 network and local services that are are putting the most load on the system, based on the processes that are running.
\n \n

User

\n \n

The up.time agent uses the following utilities to collect user information from an IRIX system:

\n \n
    \n
  • ps -eo
    • \n
  • /usr/bsd/last /usr/bsd/head -10 (login history for the last 10 users on the system)
    • \n
  • /usr/bin/who (lists who is currently logged into the system)
    • \n
\n \n
\n \n\t \n\t \n \n \n\t \n\t \n \n \n\t \n\t \n \n \n
MetricExplanation
Login HistoryThe number of times or frequency at which a user has logged into a system during any 30 minute time interval.
SessionsThe number of sessions or number of distinct users who are logged into a system during any 30 minute time interval.
  • No labels