Page History

...

Test Process

1. Delete each test "object"

...

5. Modify the datastreams a specified number of times

6. Read the datastreams

Apache Jmeter version 2.9 installed on futures1 (see Test Platform for details)

The jmeter test script fedora.jmx implements the above process for a fedora rest API.

The test data is generated at run time to produce a random binary data created from a stable set of file sizes, as explained in Test corpora - The generated binary dataset

The generation of files has been included in the jmeter test plan and does not need to be generated separately.

The Jmeter test produces a csv file (one for each repeat) containing the following columns

...

Column name	Description
timeStamp	time of request (in milliseconds since 1/1/1970 )
elapsed	time measured from just before sending the request to just after the last response has been received (in milliseconds). It does not include time taken to render the response (as on a browser).
label	the name given to the CRUD operation (in milliseconds)
responseCode	The HTTP response code received for the request
responseMessage	The HTTP response message received for the request
threadName	This is derived from the Thread Group name and the thread within the group. The name has the format groupName + " " + groupIndex + "-" + threadIndex groupName - name of the Thread Group element groupIndex - number of the Thread Group in the Test Plan, starting from 1 threadIndex - number of the thread within the Thread Group, starting from 1
dataType	the type of data received
success	a binary value indicating the success or failure of the request
bytes	the response size
Latency	The time from just before sending the request to just after the first response has been received, including all the processing time needed to assemble the request as well as assembling the first part of the response (in milliseconds).

The stats visualizations were done using R (http://www.r-project.org/).

...