Time/Place

• Time: 11:00AM Eastern Time US (UTC-4)
• 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 

• Andrew Woods 
• Yinlin Chen
• Colin Gross
• Danny Bernstein 
• Trey Pendragon 
• Longshou Situ
• Joshua Westgard

Agenda

• Christopher Johnson - bad connection

Agenda

1. Repeatable tests for demonstrating performance characteristics of Fedora

   1. Documentation
2. Review last meeting actions: See actions section below
3. Status of AWS Credits Proposal (guidelines)
4. Documentation for running tests and creating graphs
   1. : How to Conduct Performance Tests and Share Results
5. Define tests of known pain points, e.g.
   1. Performance of "many members"
   2. Ugliness of pairtree resources
   3. migration of PIDs from fcrepo3 to fcrepo4
   4. Migration from fcrepo3 to fcrepo4 in general and in a reasonable amount of time for 1M+ objects
   5. Loss of system dates, the migration of creation/modification times from fcrepo3 to fcrepo4
   6. Intra-repository referential integrity can be a pain point, but it has benefits too

Minutes

Actions

•  Colin Gross will finish up current GitHub issues: https://github.com/fcrepo4-labs/fcrepo_perf_analysis/issues
•  Danny Bernstein will create an outline of  Dos and Don'ts  and put out a message to solicit community input (cc: fedora-community list + Colin, Josh, Esme)

1. 1.  

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

2. Rerun these six tests against the current release of Fedora, 4.7.3. 

   1. An uniform experiment environment.

3. Including those tests as a part of the CI builds and/or release process
   
   1. Formalize any API performance test plan definitions in an ontology.
   2. Fedora Commons Repository - Performance Test Ontology

4. Consolidate other performance testing results.

5. Future meeting time: Does Monday 11am work or need a new time? 

6. Establishing more general performance tests against the Fedora API Specification
   

   
   

Minutes

Documenting Running Test

1. Some mismatch between fields that are being created and what the graphing script is expecting
2. Action: Colin to update scripts to support old and new spreadsheet fields
3. Action: Danny to verify and document when Colin is done

Rerun 6 tests

1. Establish three size test hardware configurations
   • small, medium, large
   • 2-cpu, 8GB memory
2. Two reasons for re-running tests
   • 1. Observing performance changes from release to release
     • Establish matrix of tests that have been run and results
   • 2. Determining the limits of Fedora (how many resources can load...)
3. Who is running each test
   • Test 2 - Danny
   • Test 3 - Andrew
   • Test 4 - Yinlin
   • Test 5 - Colin

Including tests at a part of CI builds

1. Skipped

Consolidate performance test results

1. No other results to include

When is next meeting?

1. This time is good for everyone who is here
   • Aug 14th (Monday) 11am

API Spec test suite

1. It would be helpful to have performance and compliance test suites against the Fedora API Specification
2. Interest in a proof-of-concept test framework
   • what tools and framework for compliance tests
3. Add as standing item for future agendas

HydraConnect Proposal

1. We should submit a proposal
   • https://wiki.duraspace.org/display/hydra/Samvera+Connect+2017

Actions

•  Colin to update scripts to support old and new spreadsheet fields
•  Danny to verify and document when Colin is done