Performance Testing

[wilgaboury]

The current testing just covers basic functionality, but it would be a good to add some tests that stress the pool with various combinations of parameters and measure the performance. Additionally, the current default pool size and connection limit were something I chose because they seemed reasonable, but it would better to find defaults based on empirical testing.

[wilgaboury]

Tentatively, my plan is to create a bench sub-module that will spin up an axum server with various endpoints for various redis operations. Then use Apache Bench or a similar tool to measure requests per seconds while doing some performance and heap profiling using valgrind tools (callgrind and massif).

[genusistimelord]

I mean it sounds good though for this type of testing we only really need to know how well it handles 1000 vs 1000 connections with a few different settings and a overall Speed ratio of how long it takes to do 1000 requests.

[wilgaboury]

I actually didn't realize that cargo had a built-in benchmarking functionality till I looked it up earlier. I agree, and think it would make sense to implement some benchmarks that use raw redis requests + connections before moving on to more complex tests/profiling.

[genusistimelord]

let me know when this is completed.

[wilgaboury]

Will do. Still have to make some better visualizations for the benchmark data, just haven't gotten around to it yet.