Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Performance testing is a key part of delivering a Minimum Viable Product (MVP). As part of the Hyrax Fedora 6 Working Group’s scope, we want to include performance benchmarking for key resource-intensive activities performed by Hyrax users. To reflect the current state of Hyrax adoption, the following combinations will be tested with representative performance tasks.

  • Hyrax, ActiveFedora, and Fedora 4

  • Hyrax, Valkyrie, and Fedora 6

  • Hyrax, Valkyrie and Postgres

Representative Performance-Intensive Tasks

The following activities have caused known performance issues in Hyrax with ActiveFedora and Fedora 4.x. These issues are compounded when executed in a repository with a significant amount of content already ingested, but given the challenges of generating a representative content sample in a test environment, and trying to approximate a baseline operating environment, these minimum statistics are suggested as minimum thresholds only. The activities noted below also assume a basic Hyrax installation using a default Hyrax work type/model.

  1. Bulk-ingest a work with over 150 FileSets using Bulkrax and a default Hyrax model (e.g. Generic Work)

    1. Metrics: time to complete

    2. Dependencies: Bulkrax configuration supporting a default Hyrax work type/model

  2. Bulk-ingest one or more new works using Bulkrax into a collection with over 5,000 works

    1. Metrics: time to complete

    2. Dependencies: 5,000 works must be pre-populated

  3. Add a FileSet to a work with over 150 Filesets using the Hyrax user interface

    1. Metrics: time to complete

    2. Dependencies: work with FileSets pre-populated

  4. Edit metadata for a work with over 150 FileSets

    1. Metrics: time to complete

    2. Dependencies: work with FileSets pre-populated

  5. Change visibility for a work with over 150 FileSets

    1. Metrics: time to complete

    2. Dependencies: work with FileSets pre-populated

  6. Add a work to a Collection with over 5,000 works using the Hyrax user interface

    1. Metrics: time to complete

  7. Edit metadata for a Collection with over 5,000 works

    1. Metrics: time to complete

    2. Dependencies: 5,000 works must be pre-populated and assigned to a Collection

  8. Delete a FileSet from a work with over 150 FileSets using the Hyrax user interface

    1. Metrics: time to complete

    2. Dependencies: work with FileSets pre-populated

  9. Delete a work with over 150 FileSets using the Hyrax user interface

    1. Metrics: time to complete

    2. Dependencies: work with FileSets pre-populated

  10. View a Work Page with over 150 FileSets

    1. Metrics: page load time

    2. Dependencies: work with FileSets pre-populated

  11. Navigate between page 1 and 2 on the Items list for a Work with over 150 FileSets

    1. Metrics: page load time

    2. Dependencies: work with FileSets pre-populated

  12. View a Collection Page with over 5,000 works

    1. Metrics: page load time

    2. Dependencies: 5,000 works must be pre-populated

  13. View a FileSet page attached to a work with over 150 FileSets attached

    1. Metrics: page load time

  14. Use the File Manager to re-sort FileSets for a work with over 150 FileSets attached

    1. Metrics: time to save changes

  15. Generate a IIIF manifest for a work with over 150 FileSets attached

    1. Metrics: time to complete

    2. Dependencies: image files compatible for IIIF rendering

  16. Run fixity checks on 5,000+ works

    1. Metrics: time to complete

    2. Dependencies: Fedora fixity checking configuration/rake task enabled

  • No labels