One of the deliverables of the Hyrax Fedora 6 Working Group is to gather performance testing metrics for Sirenia - a Hyrax 5.x application backed by Fedora 6.x using Valkyrie. With a nurax instance now configured and available for testing, we are looking to the community to engage and support in this testing effort.

The results of this testing will inform any future updates or improvements required and to provide baseline expectations on overall performance of the stack.

Participation is open to all users.

How to Participate:

Navigate to: https://docs.google.com/spreadsheets/d/1EsWzLPdopXn_xRGlLc7OEaxxnsvTug2o0g5I1DNIttU/edit?usp=sharing

1. Sign up for an account in f6.nurax, then contact the Hyrax Product Owner, Nick Homenda (Nicholas.Homenda@tufts.edu or @NickHomenda on Samvera Slack) to be added to the testing group. This will allow you to add, edit, and delete based on the instructions provided for each use case,, which are indicated in the Phase 1 tab of the document.

2. Grab a stopwatch to record your times.

3. Add your name to Column E or later and post the times you track for each test case.

If you have questions, you can contact the Hyrax Fedora 6 Working Group on Slack at #fcrepo

Phase 1 Test Cases

A special thanks to Juliet Hardesty at Indiana University for setting up data to use across the test cases. There are 4 available datasets to test with.

Works with over 150 files - To use one of the following works for testing, edit the work and change the title while testing (for example, remove "150" and add "IN USE").
Once testing is complete, edit the work again and change the title back to original title:

Each is identified by the following:

Parent work with over 50 child works - To use this work, edit the parent work and change the title while testing (for example, remove "50" and add "IN USE").
Once testing is complete, edit the parent work again and change the title back to original title:

Parent work with over 50 child works

If you have questions, you can contact the Hyrax Fedora 6 Working Group on Slack at #fcrepo

Phase 2 Test Cases

Bulk-ingest work with over 150 files - Template Zip file for importing a work with 152 pages (zip contains 152PageWork.csv and “files” folder with .png image files):

Open

You can use the .csv file as it is within this .zip or update source_identifer, title, and creator values. Do not change model, file, or parents values. If you do update the .csv file, you will need to create a new .zip file containing just the .csv file and the “files” folder that contains the 152 page images. See Importing from a Zip file for more details. This Zip import should add 1 work to the Smaller Bulkrax Test Collection on f6.nurax. The next test case is to delete this work so this should prevent any space issues on this testing site.

Bulk-ingest work with 1 file to collection with over 5,000 works - Template Zip file for importing a work with 1 file to Bulkrax Test Collection (zip contains 1FileWork.csv and “files” folder with 1 .png image file):

Open

You can use this .csv file as it is within this .zip or make similar updates as described with the previous .csv file. We recommend keeping this work small (only 1 file). This import will add this work to the Bulkrax Test Collection.

The final test case is one that cannot be tested on f6.nurax since the rake task to run fixity checking via the user interface is not in place. It is an optional feature to include in a Hyrax installation and while it is something to consider for performance evaluation with new versions of Fedora, it is not as high of a priority to evaluate as the other test cases and we are forgoing that test case for now on f6.nurax.