Detailed description of LR monitoring Linux system resources

Article Title: LR monitoring Linux system resource details. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.

Average load:

Average number of processes simultaneously in Ready state during the last minute

Average number of processes in the "ready" status at the same time in the last minute

Collision rate

Collisions per second detected on the Ethernet

The number of conflicts detected on the Ethernet per second.

Context switches rate

Number of switches between processes or threads, the Number of times per second switches between processes or threads per second.

CPU utilization

Percent of time that the CPU is utilized

CPU usage time percentage.

Disk rate

Rate of disk transfers

Disk transmission rate.

Incoming packets error rate

Errors per second while processing ing Ethernet packets

Number of errors received per second when an Ethernet packet is received.

Incoming packets rate

Incoming Ethernet packets per second

The number of incoming Ethernet packets per second.

Interrupt rate

Number of device interrupts per second

The number of device interruptions per second.

Outgoing packets errors rate

Errors per second while sending Ethernet packets

Number of errors sent per second when an Ethernet packet is sent.

Outgoing packets rate

Outgoing Ethernet packets per second

The number of Ethernet packets transmitted per second.

Page-in rate

Number of pages read to physical memory. per second indicates the Number of pages exchanged to physical memory per second.

Page-out rate

Number of pages written to pagefile (s) and removed from physical memory, per second indicates the Number of pages removed from the physical memory per second or written.

Paging rate

Number of pages read to physical memory or written to pagefile (s), per second reads into the physical memory per second or writes the Number of pages in the page file.

Swap-in rate

Number of processes being swapped

The number of processes exchanged to the memory per second.

Swap-out rate

Number of processes being swapped

The number of processes exchanged from the memory per second.

System mode CPU utilization

Percent of time that the CPU is utilized in system mode

The time percentage of CPU usage in system mode.

User mode CPU utilization

Percent of time CPU is utilized in user mode

The time percentage of CPU usage in user mode.

Some common problems and solutions:

1. Why does the "Deny permission" prompt appear during configuration or command installation?

A: Because of the file permission, the "777" permission should be granted to all files of the current user, that is, full control permission.

2. I cannot see the information from LoadRunner after installation, but no error is reported?

A: It may be because the returned information value is relatively small, so it is almost invisible in the figure. For example, if no program is running, the CPU usage is close to 0, so no changes can be seen in the monitoring chart. It may also be that the sampling frequency is too high. You can set the information to be retrieved once every second in the chart, so that the interface will be refreshed in a timely manner.

3. After monitoring for a period of time, the LoadRunner prompts that an error occurred and cannot continue to monitor the information?

A: The system automatically shuts down the service because the CPU is in high load for a long time. You can add a new counter in LoadRunner and set the sampling time to a little longer to avoid this situation.

4. Previously, LoadRunner monitoring was successful, but no information can be monitored again?

A: The rstatd daemon is not enabled because the system restarts. You can manually re-open the rstatd and run the "rpc. rstatd" command. You can also run the "rpcinfo-p" command to check whether the rstatd daemon has been started in the current system.

5. How can I use LR to monitor Linux windows?

This is a problem with the time settings of your graphic display. It does not matter if the lr is unstable. The specific settings are as follows: 1. run Controller 2. in the "Unix Resources" graphic window, right-click and choose Configure option 3. the "Graph Configuration" window is displayed. There is an option "Graph Time (sec)" in this window. The default value is 60 seconds. There are four options: 60 seconds, 180 seconds, 600 seconds, 3600 seconds, whole scenario (graphic data is displayed for the entire scenario)

Note: For more than 10 hours of fatigue testing, you should select whole scenario (graphic data is displayed for the entire scenario)