...
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:
- Number of resources in the repository
- Average response times of the 1000-request blocks
- Individual response times of the performance requests
Size of files
- Load different files
...
- with POST requests at the top of the repository ranging between 10KB and 10GB
- 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
- Load different files with POST requests at the top of the repository ranging between 10KB and 100KB
- After every 1000 requests, performance requests should be made
Number of containers
Create containers with POST requests at the top of the repository
- After every 1000 requests, performance requests should be made
Number of mixed resources - files and containers
Create a mix of resources representative of a typical LDP model including containers and files
- After every 1000 requests, performance requests should be made
Performance requests
- PUT a new resource
- GET the resource
- PATCH a property to the resource
- DELETE the resource