Time/Place
- Time: 11:00AM Eastern Time US (UTC-5)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
Attendees
Agenda
Performance and Scalability Test Plans
- Testing updates
- Retrieving objects that link to a large number of repository objects
- Finalizing initial tests
- Completing Tests 1, 5 and 6
- Reporting out
- Next set of tests
- Versioning
- Batch Atomic Operations
Current Summaries
Test 1 - large files
- VTech - LevelDB, 250MB, out of disk space
Test 2 - small files
- Princeton - LevelDB, 523k resources, end:too many open-files error
- Princeton - PostgreSQL, 3.9M resources, end:OOM GC
- Princeton - PostgreSQL (UseG1GC), 4.1M resources, end:Arjuna timeout
- Princeton - PostgreSQL (Mode5), 7.7M resources, end:out of disk space
- VTech - LevelDB, 250k resources, end: 500 response
- VTech - MySQL, 757k resources, end: 500 response
- VTech - PostgreSQL, 5.6M resources, end:manual stop
Test 3 - many files
- Princeton - LevelDB, 584k resources, end:Arjuna timeout
- Princeton - PostgreSQL, 1M resources, end:out of disk space
- Princeton - PostgreSQL (Mode5), 979k resources, end:out of disk space
- Princeton - PostgreSQL (Mode5.1), 975k resources, end:out of disk space
- VTech - LevelDB, 3.5M resources, end: out of disk space
- VTech - MySQL, 428k resources, end: 500 response
- VTech - PostgreSQL, 3.5M resources, end: out of disk space
- York - LevelDB, 343k resources, end:500 response (no log)
- York - MySQL (Mode5), 1.3M resources, end:MySQL lost connection
Test 4 - many containers
- Princeton - LevelDB, 737k resources, end:?
- Princeton - PostgreSQL, 3.7M resources, end:network interruption
- Princeton - PostgreSQL (Mode5), 17M resources, end:SQL persistence error
- Princeton - PostgreSQL (Mode5.1), 4.1M resources, end:manual stop
- UWMadison - ?
- VTech - LevelDB, 13M resources, end:manual stop
- York - LevelDB, 9.1M resources, end:too many open files
Test 5 - many RDF containers
- Princeton - PostgreSQL (Mode5.1), 7.2M resources, end:out of disk space
- Princeton - LevelDB, 689k resources, end:Arjuna timeout
- VTech - LevelDB, 350k resources, end: NoHttpResponseException
- VTech - MySQL, 533k resources, end: 404,Not Found
- VTech - PostgreSQL, 2.2M resources, end:manual stop
- York - MySQL, ?
Test 6 - files and containers
- None
Minutes
Testing updates
- Nick Ruest is still running Test #5 at York University
- Benjamin Armintor is working on two branches to address this issue (lower level; Modeshape level)
- Esmé Cowles is working on the issue at the Hydra level; adding inverse relationships (two pull requests are in, CurationConcerns and Sufia)
- There will be an update coming out very soon
Finalizing initial tests
Reviewed current summary:
- Test #1 - Need a test setup with enough disk space
- Test #1 - How much disk space do we need?
- Test #2 - Review what's going on with messaging; Arjuna timeout error
- Test #2 - How much disk space do we need to run these tests?
- Test #2 - Another MySQL test would be ideal (Nick Ruest will run it)
- Virginia Tech tests can only run for 7 days given the resource available. Test 1 will use another machine which doesn't have 7 days limit, but can only be used to conduct Test 1.
- Test #3 - Review what's going on with messaging; Arjuna timeout error
- Test #3 - How much disk space do we need to run these tests?
- Test #3 - Nick Ruest will look for his logs
- Test #4 - Nick Ruest will look at the reason York test failed
- Test #5 - Review what's going on with messaging; Arjuna timeout error
What concrete things can we do for further investigation?
- Determine what log files should be shared; jmeter, catalina, mysql, postgres
- jmeter; test log, perf.log, and csv file for test
- Investigate the Arjuna timeout error; Daniel Lamb to do some preliminary investigation
- Document server configuration for too-many open files (Nick Ruest first crack at it)
- Document MySQL and PostgreSQL tuning
- Look closely at the Modeshape 5 tests
- Establish common MySQL and PostgreSQL configuration, or just use default?
- PostgreSQL might have very conservative default, and may not be indicative of possible performance. Daniel Lamb to investigate.
- Andrew Woods to look at generating graphs, and what is needed.
What tests should we re-run?
- All of them, with the goal of getting highest number of resources. This would involve restarting Tomcat, or the server update test condition failure, and starting the test again.
- Identify performance trends by way of graphing