Preparations for LoadRunner testing performance in a red hat

Http://shop104965075.taobao.com

 

 

RPC-TCP: Timeout reached. (Entry Point: Factory: collectdata). [msgid: MMSG-47197]

So far.

3. parameters to be monitored in Linux

CPU metrics

Average Load

Average number of processes in the "ready" status at the same time in the last minute, <CPU count * Number of cores * 0.7

CPU utilization

CPU usage time percentage. If it is more than 75%, you can consider changing the CPU.

Swap-In Rate

Number of processes in exchange

Swap-out rate

Number of processes in exchange

Context switches Rate

Number of switches between processes or threads per second

System Mode CPU utilization

CPU usage time percentage in System Mode

User Mode CPU utilization

CPU usage percentage in user mode

Interrupt Rate

Number of device interruptions per second

Memory

Page-In Rate

Number of pages read into the physical memory per second

Page-out rate

Number of pages written to and deleted from the physical memory per second

Paging Rate

The number of pages read into the physical memory or written into the page file per second. If the number continues to be several hundred, the memory may be increased.

In the data collected by LoadRunner, memory usage is not available. Sar can be installed and then observed by SAR:

You can use this command to SAR-N Dev-u-r 3 120> perform. Log

This command sample once every 3 seconds, 120 times 360 seconds = 6 minutes, you can adjust the values 3 and 120 as needed. Perform. log is the saved file name.

Disk

Collision rate

Number of conflicts detected on the Ethernet per second

Disk Rate

Disk Transfer Rate

Network

Incoming packets Error Rate

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

Incoming packets Rate

Number of incoming Ethernet packets per second

Outgoing packets errors Rate

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

Outgoing packets Rate

Number of Ethernet packets transmitted per second

PPS is

The minimum packet length for Ethernet transmission is 64 bytes. The packet forwarding speed is measured by the number of 64 bytes of data packets (minimum packet) sent per unit time.

For Gigabit Ethernet, the calculation method is as follows:

1000 Mbps/(64b + 8B + 12B) × 8bit) = 1.488095pps

Note: When the Ethernet frame is 64 byte, the fixed overhead of the 8 byte leading character and the 12 byte frame gap must be considered.

In Ethernet, each frame header must contain an 8-byte leading character, which is used to tell the listener that data is coming. Then, there must be a frame gap between each frame in the Ethernet, that is, after each frame is sent, wait for a while before another frame is sent. In the Ethernet standard, the minimum value is 12 bytes, however, the frame gap may be larger than 12 bytes in practice. Here I use the minimum value. Each frame has a fixed overhead of 20 bytes. (In addition, the 20 bytes of information cannot be captured by the packet capture software)

Therefore, the packet forwarding rate of a full-duplex Gigabit Ethernet port when forwarding 64 bytes of packets is 1.488 mpps.

The following is a packet forwarding rule for common Ethernet ports:

1. 10 Gigabit Ethernet: 14.88 mpps

2. ge Ethernet: 1.488 mpps

3. 0.1488 Mbps Ethernet: mpps

4. 10G Ethernet: 0.01488 mpps (14.88 KPPS)

Http://www.beyondtest.com/Item/Show.asp? M = 1 & D = 2419

 

Basic Steps for Performance Testing

Http://shop104965075.taobao.com

Http://www.docin.com/p-308940183.html