...
- 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
...
Panel |
---|
Test 1 - large files
Test 2 - small files
Test 3 - many files
Test 4 - many containers
Test 5 - many RDF containers
Test 6 - files and containers
|
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