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
Agenda
- Christopher Johnson - bad connection
Agenda
Repeatable tests for demonstrating performance characteristics of Fedora
- Documentation
- Review last meeting actions: See actions section below
- Status of AWS Credits Proposal (guidelines)
- Documentation for running tests and creating graphs
- Define tests of known pain points, e.g.
- Performance of "many members"
- Ugliness of pairtree resources
- migration of PIDs from fcrepo3 to fcrepo4
- Migration from fcrepo3 to fcrepo4 in general and in a reasonable amount of time for 1M+ objects
- Loss of system dates, the migration of creation/modification times from fcrepo3 to fcrepo4
- 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)
-
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2424
-
Rerun these six tests against the current release of Fedora, 4.7.3.
An uniform experiment environment.
- Including those tests as a part of the CI builds and/or release process
- Formalize any API performance test plan definitions in an ontology.
- Fedora Commons Repository - Performance Test Ontology
Consolidate other performance testing results.
Future meeting time: Does Monday 11am work or need a new time?
Establishing more general performance tests against the Fedora API Specification
Minutes
Documenting Running Test
- Some mismatch between fields that are being created and what the graphing script is expecting
- Action: Colin to update scripts to support old and new spreadsheet fields
- Action: Danny to verify and document when Colin is done
Rerun 6 tests
- Establish three size test hardware configurations
- small, medium, large
- 2-cpu, 8GB memory
- 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...)
- 1. Observing performance changes from release to release
- 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
- Skipped
Consolidate performance test results
- No other results to include
When is next meeting?
- This time is good for everyone who is here
- Aug 14th (Monday) 11am
API Spec test suite
- It would be helpful to have performance and compliance test suites against the Fedora API Specification
- Interest in a proof-of-concept test framework
- what tools and framework for compliance tests
- Add as standing item for future agendas
HydraConnect Proposal
- We should submit a proposal
Actions
- Colin to update scripts to support old and new spreadsheet fields
- Danny to verify and document when Colin is done