Feature #2580
Updated by Tim Pierce about 10 years ago
In addition to unit tests, we need to be able to demonstrate Keep performance by means of a stress test.
A stress test should:
* Flood Keep with concurrent GET and PUT requests
* Record performance metrics including:
** Number of successful requests
** Number and breakdown of error results
** Shortest, longest, and median response time
** Any inconsistencies on Keep volumes after testing is done
* Configurable options could include:
** Maximum concurrency for requests (e.g. @--concurrency=50@ means max 50 requests at a time)
** SSL or non-SSL
A useful experiment would be to perform stress tests with the same parameters against new Keep and old Keep.