Testing Profiles
To make our testing as repeatable as possible, we have created profiles for various parts of the testing setup:
- Platform Profiles - the hardware and networking used to conduct the tests
- Repository Profiles - the Fedora-specific configuration options
- Setup Profiles - the data loaded into the repository as a baseline before testing
- Workflow Profiles - the specific tests performed, what tools were used, and what was measured
A performance test scenario consists of the intersection of a profile of each type: a platform profile, a repository profile, a setup profile, and a workflow profile. Performance test results will indicate which profiles were used when the tests were run.
Test Results
- Single-Node Test Results - directly comparing ingest/read/update/delete times of Fedora 3 and Fedora 4, on a single server.
- Clustered Performance Testing - comparing ingest/read/update/delete times of a cluster of Fedora 4 servers.
- Large File Ingest and Retrieval - testing ingesting and serving files as large as 1TB.
- AuthZ - No AuthZ Fedora 4 Comparison Performance Testing - testing the impact of enabling authorization on ingest/read/update/delete performance.
- Flat Hierarchies Testing - testing load times on ten to thirty thousand containers when there is no hierarchy
- Fedora 4 Properties CRUD Performance Testing - testing the time it takes to perform create/read/update/delete operations on resource properties
This section collects defined performance test profiles along with templates and advice for creating new ones.