...

1. Updates
   1. Tickets
      

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1947

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1948

      3. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1949

      4. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1950

      5. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1951

      6. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1952

      7. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1953

      8. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1954

      9. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1956

   2. Results
      1. Princeton Results - Test 4
      2. UW Madison Results - Test 4
      3. York University Results - Test 4
   3. What lessons have we learned from tests already run?

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1880

      2. Nick Ruest, Martin Haye: Ingest slowdown after x-number or resources loaded
2. Create a quick start guide for running the tests?
   1. https://gist.github.com/ruebot/f1979ba1e1ad1e519541c2aeb3b49f2c
   2. A vagrant box with Puppet that installs Fedora 4. Less complete than Nick's guide above for tests, but different environment (CentOS, OpenJDK). https://github.com/nulib/fcrepo4-vagrant
3. YourKit profiling
4. Modifying/adapting tests for Islandora and Hydra testing
5. Hack-house event in the Fall?
6. It would be great to have performance baselines before transitioning to Modeshape5
7. ...

Minutes

Tickets

• Need to create tests 5 and 6
• Self-assign tickets for running tests
• Scott will do MySQL and PostgreSQL
• Martin to run Test - 4
  • Not necessary to run on AWS
  • Best to run on remote machine
  • JMeter client also consumes resources, best to have on separate machine
• Test-1
  • Aaron to update documentation for running this
• Remove Test-3

Results

Princeton

• leveldb - 737k resources before failure
  • slightly faster than an untuned postgres
• postgres - never timed out, 3.7mil before network disconnect
  • opportunity for tunning, was tested with stock install
    • adding index on key would help
• determine units of jmeter results

Madison

• Focused on resource consumption
• Ran for ~48 hours
• CPU settled down after initial warm-up
• Will use jmeter graphing component next
• Will retrieve the number of resources created

York

• Timed out at 2.5mil resources
• Restarted tomcat and updated max file handles
  • reached ~9.4mil resources
• Used leveldb
• It would be useful to run tests with alternate GC flags

Lessons learned

• -XX:+UseG1GC
• See http://www.oracle.com/technetwork/tutorials/tutorials-1876574.html
• Martin would like to run Test-4 in different memory configurations

Islandora/Hydra testing

• testing with interaction patterns based on these upper apps

hack house

• maybe in the fall

Actions

• Esme to run other tests (1 and 2)
• Martin to run test 4
• Nick to run other tests pending documentation from Aaron
• Aaron to add docs next week
• Scott, test 4, jmeter graphing
• Yourkit: Scott, UMd?, Doron, Nick
  • Steve: vagrant to deploys F4

Next meeting

• May 16th next meeting