- Review last meeting actions:
- Colin Gross to transfer fcrepo_perf_analysis to fcrepo4-labs
- Andrew Woods to post test outputs to S3
- Colin Gross to push outputs from R-scripts to GitHub
- Nick Ruest and Yinlin Chen to take above R-script output as starting point for performance test summary report
- Review current GitHub issues: https://github.com/fcrepo4-labs/fcrepo_perf_analysis/issues
- Infrastructure options - Research Grant
- AWS Cloud Credits for Research https://aws.amazon.com/research-credits/ Rewards varies from 1 to 2 years.
- Reproduce new performance report?
- If anyone what to know current Fedora 4.7 performance, we can refer him to see the performance report page.
- Performance and Scalability Test Plans
- Baseline performance on these six scenarios in a:
- Select an instance type in AWS
- other options?
- An Ansible tool to install Fedora 4 on the local machine or AWS.
- 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