fcrepo4-jmeter

Description

This repository contains JMeter configurations for the Fedora4 Performance and Scalability group.

Test plans can be found here.

Usage

To run these Fedora JMeter tests, download JMeter and execute:

./jmeter -Dfedora_4_username=<default=fedoraAdmin> -Dfedora_4_password=<default=fedoraAdmin> -Dfedora_4_server=<default=localhost> -Dfedora_4_context=<default=rest> -n -t <path/to/fcrepo4-jmeter>/fedora.jmx

..where-n specifies "non-GUI mode", and -t specifies the location of the test "jmx" file.

The following is an example running a test against a remote Fedora deployed under the "fcrepo" context:

./jmeter -Dfedora_4_server=52.90.98.146 -Dfedora_4_context=fcrepo/rest -n -t fedora.jmx

If Fedora is deployed using HTTPS, specify the protocol and port on the command line:

./jmeter -Dfedora_4_username=<default=fedoraAdmin> -Dfedora_4_password=<default=fedoraAdmin> -Dfedora_4_protocol=https -Dfedora_4_port=8443 -Dfedora_4_server=<default=localhost> -Dfedora_4_context=<default=rest> -n -t <path/to/fcrepo4-jmeter>/fedora.jmx

Running specific performance tests

This JMeter configuration can be used for several of the test plans

By default, no tests will run; tests are configured via command-line variable definitions. To run any tests, you must set the number of threads to use to a non-zero number via -Dbinary_threads or -Dcontainer_threads. If both are set to nonzero, first the 'Create new containers' test will run, followed by an attempt to run the Create binary resource test.

Test 1 - Size of files - large

The maximum filesize of 10GB as specified in the test plans does not currently seem to work for a couple reasons:

• the uploaded file is currently a single array, and Java has an array limit of between 1 and 2 billion elements
• JMeter's HTTP sampler holds the entire request in memory at once The practical upper limit seems to be around 500MB, which still requires 6-8GB of heap for JMeter.o

Also, generating large random files is CPU-bound, so it's especially preferable for this test to run jmeter on a separate machine from Fedora. Network bandwidth is then likely to be the limiting factor - the underlying RandomStringUtils implementation can generate about 100MB/second of random data on a i7 3770.

(Ideally instead of generating the entire file at once, we could generate small chunks at a time and just have the sampler read them from an InputStream, but that doesn't seem to be possible with the default JMeter HTTP sampler.)

To run with one thread uploading files between 10KB and 500MB to Fedora:

• Run:

JVM_ARGS=-Xmx8G jmeter -Dfedora_4_username=<default=fedoraAdmin> -Dfedora_4_password=<default=fedoraAdmin> -Dfedora_4_server=<default=localhost> -Dfedora_4_context=<default=rest> -Dfilesize_min=10000 -Dfilesize_max=500000000 -Dbinary_threads=1 -n -t <path/to/fcrepo4-jmeter>/fedora.jmx

Test 2 - Size of files - small

• Run:

jmeter -Dfedora_4_server=<default=localhost> -Dfedora_4_context=<default=rest> -Dfilesize_min=0 -Dfilesize_max=4096 -Dbinary_threads=1 -n -t <path/to/fcrepo4-jmeter>/fedora.jmx

Test 3 - Number of files

• Run:

jmeter -Dfedora_4_server=<default=localhost> -Dfedora_4_context=<default=rest> -Dfilesize_min=10000 -Dfilesize_max=100000 -Dbinary_threads=1 -n -t <path/to/fcrepo4-jmeter>/fedora.jmx

Test 4 - Number of containers - default

• Run:

jmeter -Dfedora_4_server=<default=localhost> -Dfedora_4_context=<default=rest> -Dcontainer_threads=1 -n -t <path/to/fcrepo4-jmeter>/fedora.jmx

Test 5 - Number of containers - with RDF bodies

• Run:

jmeter -Dfedora_4_server=<default=localhost> -Dfedora_4_context=<default=rest>  -Dresource_directory=<default=.> -Dcontainer_rdf_threads=1 -n -t <path/to/fcrepo4-jmeter>/fedora.jmx