parallaxsecond/parsec-client-test

Parsec client test

parsec-client-test's Issues

Implement a stress test client

Stress tests are needed to ensure thatt he parsec service is resilient to heavy loads. A stress client would be a good addition to the test client family.

Stress Client Design Proposal

The StressTestClient will be more like a thread pool manager, spinning up a configurable number of threads that each act as a parsec client. The tasks in each thread will be executed by a StressWorker. One last thread will act as a ServiceChecker.

StressWorkers will generate a fixed number of random requests with a configurable delay between them. Not relevant at the moment, but for the future the workers can be expanded to randomly choose between providers as well.
Each worker generates an identity for itself at creation and then preserves that identity throughout the test.

The response status for the requests is relevant only as far as ensuring that the request was processed by the provider. An example would be signature verification, where the validity of the data provided as signature is irrelevant.

The ServiceChecker's job is to assess the status of the service periodically. It will go through a sign and verify test every time, making sure that the response is valid.

In the future, the checker could be expanded to keep track of response time. It could also actively collect statistics about the service process - e.g. CPU and memory usage.

The StressTestClient will not be immediately integrated in a CI test, but rather kept for testing on real hardware.

Update to use new interface

After the updates to the protobuf contracts and the subsequent changes to the interface, the test client should be updated to use the new available API.

Refactor to use the new Rust client

A Rust client is going to be created parallaxsecond/parsec#127, this repository should be based on it and only contain the specific methods that are only useful for testing.

Wait for the service to be ready

The client should wait that the socket is created (with a timeout) before doing any operation. This will prevent having to put sleep in the CI test script.