"Go" jmeter Project test

 

　　The Jmeter recording playback feature is now recording your history of access to the items you want to test , and then virtual out multiple users replay the history to achieve stress testing purposes.

Recording is recorded through a proxy server.

One

Http://labs.xiaonei.com/apache-mirror/jakarta/jmeter/binaries/jakarta-jmeter-2.3.2.zip

Second, the installation of JMeter is very simple, download from the official website, after decompression can be used. Run the command under%jmeter_home%/bin, for Windows users, the command is Jmeter.bat.

Third, recording.

1) Create a new proxy server.

Set the port [8080].

Regular expressions fill in the exclusion mode (optional).

I.. *-All

Ii.. *.png–png Images

Iii.. *.gif–gif Images

Iv.. *.jpg–jpeg Images

V.. *.php

Vi.. *.jsp

Vii.. *.html

Viii.. *.htm

Ix.. *.js

2) browser settings on this proxy server

Internet Options – Connection--LAN Settings localhost:8080

3) The proxy server is set up so that you can start to set up thread groups

In the right window, set the number of threads (equivalent to the number of virtual users) to 50,ramp-up Period (in seconds, Interval time, set to 0 for concurrent access) to 0, and enter 2 in the Loop box. The above settings represent a total of 50 virtual users, concurrent access, iteration 2 times

4) Adding a recording controller to a thread group

5) Start the proxy server.

Start the proxy server so that the records accessed in the browser where the proxy is set will be recorded by the logger and displayed below the logger to see the path, parameters, etc. of the access.

Iv. playback test and result query

Add an aggregated report for the thread group to view the results

Cancel the IE proxy and stop the agent.

Run start to see the stress test data in the aggregation report.

Label: Each JMeter element (for example, HTTP Request) has a name attribute, which shows the value of the Name property

#Samples: Indicates how many requests you have made in this test, and if you simulate 10 users, each user iterates 10 times, then this shows a 100

Average: Average response time--the average response time of a single Request by default, or the average response time in Transaction when a Transaction Controller is used

Median: Median, which is the response time of 50% users

90% line:90% User's response time

Min: Minimum response time

Max: Maximum response time

error%: Number of requests with errors in this test/total number of requests

Throughput: Throughput--By default, indicates the number of requests completed per second (request per Second), and when Transaction Controller is used, it can also represent LoadRunner -like Transaction per Second number

Kb/sec: The amount of data received from the server side per second, equivalent to throughput/sec in LoadRunner

A problem occurred after adding a proxy server: Connect to localhost hint: server localhost in XDB requires user name and password, this problem occurs because of installation of Oralce. The Xdb feature is included by default when Oracle 9i creates a database. Once the database is started and the Listener,oracle Xdb starts the HTTP service. Xdb HTTP Service occupies 8080 ports, just like JBoss, Tomcat and other default ports conflict, Oracle XDB port settings are not in the configuration file, but in the database. That is the main reason, and there may be other reasons, of course.

Here's how to fix it:

1. Open services.msc, turn off the ORALCESERVICEYOURORACLESID server, complete the test first, and then turn on the service when you need to use Oracle.

2, modify the port number of the XDB server can also achieve the purpose, the steps are as follows

The method of disabling Oracle's XDB service is simple, removing the corresponding initialization parameters for the database:

Edit the $oracle_home/dbs/initsid.ora file to remove the following line:

Dispatchers= ' (protocol=tcp) (SERVICE=XDB) '

Restart database

Shutdown immediate;

Create SPFile from Pfile;

Startup

To modify the XDB service port:

Xdb HTTP Service occupies 8080 ports, just like JBoss, Tomcat and other default ports conflict, Oracle XDB port settings are not in the configuration file, but in the database. Modify the HTTP and FTP service ports for XDB as follows:

Using SYS login Sqlplus, modify port settings with Dbms_xdb

Sql>-change the Http/webdav port from 8080 to 8081

Sql> Call Dbms_xdb.cfg_update (Updatexml (

2 Dbms_xdb.cfg_get ()

3, '/xdbconfig/sysconfig/protocolconfig/httpconfig/http-port/text () '

4, 8081))

5/

Call completed.

Sql>-change the FTP port from 2100 to 2111

Sql> Call Dbms_xdb.cfg_update (Updatexml (

2 Dbms_xdb.cfg_get ()

3, '/xdbconfig/sysconfig/protocolconfig/ftpconfig/ftp-port/text () '

4, 2111))

5/

Call completed.

Sql> COMMIT;

Commit complete.

Sql> EXEC Dbms_xdb.cfg_refresh;

PL/SQL procedure successfully completed.

"Go" jmeter Project test