Apache JMeter may be used to test performance both on static and dynamic resources, Web dynamic applications. It can be used to simulate a heavy load on a server, group of servers, network or object to test its strength or to analyze overall performance under different load types.
Apache JMeter features include:
Ability to load and performance test many different applications/server/protocol types:
Full featured Test IDE that allows fast Test Plan recording (from Browsers or native applications), building and debugging.
Command-line mode (Non GUI / headless mode) to load test from any Java compatible OS (Linux, Windows, Mac OSX, ...)
A complete and ready to present dynamic HTML report
Live reporting into 3rd party databases like InfluxDB or Graphite
Easy correlation through ability to extract data from most popular response formats, HTML, JSON, XML or any textual format
Complete portability and 100% Java purity
Full multi-threading framework allows concurrent sampling by many threads and simultaneous sampling of different functions by separate thread groups.
Caching and offline analysis/replaying of test results.
Highly Extensible core:
Details of the latest version can be found on the JMeter Apache Project web site (https://jmeter.apache.org/).
The following requirements exist for running Apache JMeter:
Java Interpreter:
A fully compliant Java 8 Runtime Environment is required for Apache JMeter to execute. A JDK with keytool utility is better suited for Recording HTTPS websites. Java 9 is not yet supported as of version 3.3.
Optional jars:
Some jars are not included with JMeter. If required, these should be downloaded and placed in the lib directory
Java Compiler (OPTIONAL):
A Java compiler is not needed since the distribution includes a precompiled Java binary archive. Note that a compiler is required to build plugins for Apache JMeter.
Note that spaces in directory names can cause problems.
Release builds
Unpack the binary archive into a suitable directory structure.
bin directoryjmeter (Un*x) or jmeter.bat (Windows) file.For Windows there are also some other scripts which you can drag-and-drop a JMX file onto:
jmeter-n.cmd - runs the file as a non-GUI testjmeter-n-r.cmd - runs the file as a non-GUI remote (client-server) testjmeter-t.cmd - loads the file ready to run it as a GUI testThe documentation available as of the date of this release is also included, in HTML format, in the printable_docs/ directory, and it may be browsed starting from the file called index.html.
See Issue Tracking
Unpack the source archive into a suitable directory structure. Most of the 3rd party library files can be extracted from the binary archive by unpacking it into the same directory structure. You can also use Ant to download the required library files:
ant download_jars
Any optional jars (see above) should be placed in lib/opt and/or lib.
Jars in lib/opt will be used for building JMeter and running the unit tests, but won't be used at run-time.
This is useful for testing what happens if the optional jars are not downloaded by other JMeter users.
If you are behind a proxy, you can set a few build properties in build-local.properties for ant to use the proxy:
proxy.use=true proxy.host=proxy.example.invalid proxy.port=8080 proxy.user=your_user_name proxy.pass=your_password
You might also want to skip some tests - that are failing without proper access to the internet - by adding some more properties into build-local.properties:
skip.bug52310=true skip.bug60607=true skip.batchtest_Http4ImplPreemptiveBasicAuth=true skip.batchtest_SlowCharsFeature=true skip.batchtest_TestKeepAlive=true skip.batchtest_ResponseDecompression=true skip.test_http=true skip.test_TestDNSCacheManager.testWithCustomResolverAnd1Server=true
JMeter is built using Ant.
Change to the top-level directory and issue the command:
ant download_jars
This only needs to be done once; it will download any missing 3rd party jars.
ant
This will compile the application and enable you to run jmeter from the bin directory.
ant test [-Djava.awt.headless=true]
This will compile and run the unit tests. The optional property definition is required if the system does not have a suitable GUI display.
Building and contributing is explained in details at https://jmeter.apache.org/building.html
The code is maintained in SVN at https://svn.apache.org/repos/asf/jmeter/trunk
There is a read-only mirror at GitHub: https://github.com/apache/jmeter
For legal and licensing information, please see the following files:
This distribution may include software that has been designed for use with cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information.
The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.
The following provides more details on the included software that may be subject to export controls on cryptographic software:
Apache JMeter interfaces with the Java Secure Socket Extension (JSSE) API to provide
- HTTPS support
Apache JMeter interfaces (via Apache HttpClient4) with the Java Cryptography Extension (JCE) API to provide
- NTLM authentication
Apache JMeter does not include any implementation of JSSE or JCE.
Thank you for using Apache JMeter.