JMeter stress testing

JMeter stress testing

Overall goal:

Install the virtual machine, and install a LAMP (Linux + Apache + Mysql + PHP) to test the system, we recommend ECShop (http://www.ecshop.com), based on this Jmeter pressure test, the Jmeter test report is obtained after the test, and the CIMN (CPU, IO, Memory, and Network) performance of the Linux server is obtained based on sysstat.

Division of labor:

1. Role 1: Install LAMP: Linux Server (CentOS), Apache, and PHP

2. Role 2: Install MySQL and ECShop (or a system similar to the B/S structure)

3. Role 3: Install sysstat and use sysstat to view the CIMN (CPU + IO + Memory + Network) performance of the Linux server, Linux system performance, and use the activity monitoring tool-Sysstat

4. Role 4: Use Jmeter to perform 5*10, 50*20 stress tests and generate a Jmeter Aggregate Report. Use sysstat to collect statistics on server information.

You may also like the following LAMP-related content:

Install Xcache and Memcached on the LAMP platform to accelerate website operation

Build a LAMP platform environment in CentOS 7

CentOS 6.5 system installation and configuration LAMP (Apache + PHP5 + MySQL) server environment

Configure the LAMP + phpMyAdmin PHP (5.5.9) development environment in Ubuntu 14.04

Install LAMP in Ubuntu 14.10

LAMP combines NFS to build a small blog site

Lab content:

In this experiment, we need to install Ubuntu on one of our machines, configure Apache2, PHP5, and MySQL on this machine, and then install ECShop and sysstat as servers, install Jmeter on another machine, use the recording script to access the ECShop website built on the server side, and view the server performance through sysstat on the server side. Finally, the report is obtained on the client and server respectively.

1) Linux top command results

2) accessed B/S system

 

 

3) Expand the Testplan of Jmeter

4) Beanshell code

5) Aggregate Report Result after Jmeter test is run

5*10 as an example:

6) server performance after Jmeter Test

We can use the 'Sar 'command to obtain the overall system performance report. This helps us locate system performance bottlenecks and find solutions to these annoying performance problems.

The Linux kernel maintains some internal counters that contain information such as all requests, their completion time, and the number of I/O blocks. The sar command calculates the request utilization and proportion from all these information, to identify the bottleneck.

The main purpose of the sar command is to generate reports of all activities in a certain period of time.

Sar command introduction sar-h usage: sar [Options] [<interval> [<times>] main options and reports: -B I/O and transmission rate Information Status-B paging condition-d Block device status-I {<interrupt> | SUM | ALL | XALL} interrupt Information Status-m Power Management Information Status -n {<keyword> [,...] | ALL} network statistics keyword can be: DEV Nic edev nic (error) NFS client nfsd nfs server SOCK Sockets (socket) (v4) IP stream (v4) EIP stream (v4) (error) ICMP stream (v4) eicmp icmp stream (v4) (error) TCP stream (v4) etcp tcp stream (v4) (error) UDP stream (v4) SOCK6 Sockets (socket) (v6) IP6 IP stream (v6) EIP6 IP stream (v6) (error) ICMP6 ICMP stream (v6) EICMP6 ICMP stream (v6) (error) UDP6 UDP stream (v6) -q queue length and average load-r memory utilization-R memory condition-S swap space utilization-u [ALL] CPU utilization-v Kernel table condition-w task creation and System Conversion statistics -W switch information-y TTY device status

Use JMeter to perform a stress test on WebService

JMeter Installation notes in Windows

Use JMeter for basic stress testing

How to Use assertions in JMeter

This article permanently updates the link address: