- Time: 11:00am Eastern Standard Time US (UTC-5)
- Dial-in Number: (712) 775-7035
- Updates
- Tickets
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Results
- Princeton Results - Test 4
- UW Madison Results - Test 4
- York University Results - Test 4
- What lessons have we learned from tests already run?
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Nick Ruest, Martin Haye: Ingest slowdown after x-number or resources loaded
- Create a quick start guide for running the tests?
- https://gist.github.com/ruebot/f1979ba1e1ad1e519541c2aeb3b49f2c
- 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
- YourKit profiling
- Modifying/adapting tests for Islandora and Hydra testing
- Hack-house event in the Fall?
- It would be great to have performance baselines before transitioning to Modeshape5
- ...
- 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
- 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
- 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
- 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
- testing with interaction patterns based on these upper apps