The following tests are designed to demonstrate how "performance" of the Fedora repository changes as the size of the repository grows under various, but discrete uses.

Note: "Performance" will be measured by requesting CRUD operations after every x-number of ingest events.

Setup

Along with the following tests, the following items will also be documented:

• Version of Fedora
• Fedora configuration details
• System details (OS, memory, hardware specs or virtualization, JVM, etc)
• Initial state of the repository
• Number of client processes/threads (ideally clients are on a separate machine)

Tests

The following measurements should be recorded:

1. Number of resources in the repository
2. Average response times of the 1000-request blocks
3. Individual response times of the performance requests

Size of files

1. Load different files with POST requests at the top of the repository ranging between 10KB and 10GB
2. After every 1000 requests, performance requests should be made

Note: Fedora stores files based on their SHA1. In order for this test to be effective, each file should have a different SHA1.

Number of files

1. Load different files with POST requests at the top of the repository ranging between 10KB and 100KB
2. After every 1000 requests, performance requests should be made

Number of containers

1. Create containers with POST requests at the top of the repository

2. After every 1000 requests, performance requests should be made

Number of mixed resources - files and containers

1. Create a mix of resources representative of a typical LDP model including containers and files

2. After every 1000 requests, performance requests should be made

Performance requests

1. PUT a new resource
2. GET the resource
3. PATCH a property to the resource
4. DELETE the resource