Princeton Results - Test 5

Setup

1. Version of Fedora
   1. 4.5.2-SNAPSHOT | Build #4f31e2f9 (2016-06-28) (modeshape5 branch with update to 5.1 from awoods:fcrepo-2062)
2. Fedora Configuration
   1. JAVA_OPTS="${JAVA_OPTS} -Dfcrepo.modeshape.configuration=classpath:/config/jdbc-postgresql/repository.json -XX:+UseG1GC -XX:+DisableExplicitGC"
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

   7. 100GB disk, about 70GB free at beginning of test
   8. Database: PostgreSQL 9.5 running on the same VM as Fedora
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).
• Because of an error in fedora.jmx, the filesize_max value was the default value (100000).

Results

PostgreSQL (Modeshape 5.1)

1. Summary: 7,255,457 in 262,240s = 27.7/s, Avg: 31, Min: 1, Max: 2,173, Err: 1 (0.00%)
2. Status: Test finished when the VM ran out of disk space and PostgreSQL could not insert data.
3. Logs:
1. test5-postgres-mode5.log

2. test5-postgres-mode5.csv.gz

3. test5-postgres-mode5-perf.log

LevelDB

1. Version of Fedora: Release: 4.5.1 | Build #8603e815 (2016-04-29)
2. Summary: 689,328 in 22,574s = 30.5/s, Avg: 28, Min: 8, Max: 520, Err: 1 (0.00%)
3. Status: Test finished when Fedora encountered the error: WARN 20:37:14.467 (arjuna) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff7f000101:abc7:5783e327:29e842 in state  RUN
4. Logs:
   1. test5-leveldb.log
   2. test5-leveldb.csv.gz
   3. test5-leveldb-perf.log