Setup
- Version of Fedora
- 4.5.2-SNAPSHOT | Build #4f31e2f9 (2016-06-28) (modeshape5 branch with update to 5.1 from awoods:fcrepo-2062)
- Fedora Configuration
JAVA_OPTS="${JAVA_OPTS} -Dfcrepo.modeshape.configuration=classpath:/config/jdbc-postgresql/repository.json
-XX:+UseG1GC -XX:+DisableExplicitGC"
- System details
- Fedora: VMWare VM configured with 4x 2.8GHz CPU, 16GB RAM
- JMeter: separate identical VM
Network: 1000Mb/s ethernet
OS: Ubuntu 14.04.3 LTS
JVM: Oracle JDK 1.8.0_66-b17
Servlet container: Tomcat 7.0.52
- 100GB disk, about 70GB free at beginning of test
- Database: PostgreSQL 9.5 running on the same VM as Fedora
- Initial State of the Repository
- empty
- Number of Client Threads
- 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)
- Summary:
7,255,457 in 262,240s = 27.7/s, Avg: 31, Min: 1, Max: 2,173, Err: 1 (0.00%)
- Status: Test finished when the VM ran out of disk space and PostgreSQL could not insert data.
- Logs:
LevelDB
- Version of Fedora: Release: 4.5.1 | Build #8603e815 (2016-04-29)
- Summary:
25,028 in 839s = 29.8/s, Avg: 28, Min: 10, Max: 520, Err: 0 (0.00%)
- Status: Test currently running