Princeton Results - Test 2

Setup

1. Version of Fedora
   1. 4.5.1-SNAPSHOT | Build #fd6f9da9 (2016-02-19) (https://github.com/fcrepo4/fcrepo4/pull/986 before squashing)
2. Fedora Configuration

   1. JAVA_OPTS="-Dfcrepo.home=/var/lib/tomcat7/fcrepo4-data -Djava.awt.headless=true -Xmx8g"

   2. See below

3. System details
   1. Fedora: VMWare VM configured with 4x 2.8GHz CPU, 16GB RAM
      
   2. JMeter: separate identical VM

   3. Network: 1000Mb/s ethernet

   4. OS: Ubuntu 14.04.3 LTS

   5. JVM: Oracle JDK 1.8.0_66-b17

   6. Servlet container: Tomcat 7.0.52

4. Initial State of the Repository
   1. empty
5. Number of Client Threads
   1. 1

Test

$HOME/jmeter/bin/jmeter -Dfilesize_min=0 -Dfilesize_max=4096 -Dfedora_4_server=lib-fedora1 -Dfedora_4_context=fcrepo/rest -n -t $HOME/jmeter/fedora.jmx

• fedora.jmx edited according to instructions in fcrepo4-jmeter PR #4 (enabling "Fedora4 Create Binary Resource" thread group and disabling all others).

Results

LevelDB

1. Summary: 584,923 in 20,746s = 28.2/s, Avg: 29, Min: 8, Max: 4202, Err: 1 (0.00%)
2. Status: Test ended when Fedora encountered the error "ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff7f000101:ecc1:5737143c:238f73 in state  RUN"
3. Logs:
   1. jmeter log: test2-leveldb.log
   2. jmeter data: test2-leveldb.csv.gz
   3. jmeter perf: test2-leveldb-perf.log
   4. fedora log: test2-leveldb-fedora.log.gz

PostgreSQL

1. Additional config: 
   1. JAVA_OPTS="${JAVA_OPTS} -Dfcrepo.modeshape.configuration=classpath:/config/jdbc-postgresql/repository.json"
   2. PostgreSQL 9.3 running on same VM as Fedora
2. Summary: 1,019,512 in 53,750s = 19.0/s, Avg: 46, Min: 8, Max: 4618, Err: 1 (0.00%)
3. Status: Test ended when Fedora ran out of disk space (approx. 70GB)
4. Logs:
   1. jmeter log: test2-postgres.log
   2. jmeter data: test2-postgres.csv.gz
   3. jmeter perf: test2-postgres-perf.log
   4. fedora log: test2-postgres-fedora.log.gz