...
The scenarios are broken into major categories of use that give us examples of how Fedora is used to aid in constructing a realistic performance test suite. These are intended to be pragmatic categories since they present different loads on the system and should not be mechanically linked one-to-one with any API.
Definitions
- Use - Core action in a use case from the user's view
- User Operation - Users view of a logical, single operation
- Repository Operation - Repositories view of a logical, single operation
- Performance - The number of units of work that are accomplished during an operation
- Interleaving - The number and kinds of operations being performed at the same nominal time (as opposed to a single repetition of an operation)
- Unit of Work - A metric to be defined appropriate to the Fedora Repository.
- There may be more than one metric
- Working definitions:
- The amount in bytes of content and metadata for an operation, or per unit of time
- The number of operations per unit of time
- The time between when an operation is started and when it is completed
...
Repository Operations
- TBD - Map to API
Testing Matrix
Category | Uses | APIs | Test Metric | Test | Notes |
---|---|---|---|---|---|
Authoring | |||||
Simple Ingest | Large Files | Duration | |||
Simple Ingest | Large Files | Rate | |||
Bulk Ingest | Large Files |
Testing Considerations
These scenarios expand on the previous single stimulus tests to use multiple read, write, and read-write tests via the REST api.
...