Corvus Redis Cluster Proxy

To build Corvus from the latest source, you must first clone the repository and initialize submodules. You will need autoconf installed to handle dependencies.

1. Clone the repository.
2. Initialize submodules.
3. Install dependencies using make deps.
4. Build the binary using make.

The resulting binary is located at ./src/corvus.

git clone https://github.com/eleme/corvus.git
cd corvus
git submodule update --init
make deps # need autoconf
make

Corvus performance is evaluated using redis-benchmark to measure capacity under extreme load. These tests focus on maximum operational load rather than service quality (latency/return time). Detailed benchmark results for specific operations are available in the following reports:

• set
• get
• mset

You can benchmark the MSET command in Redis using the redis-benchmark utility. This allows you to test the performance of multi-set operations by specifying the host, port, number of requests, rate, command type, payload size, and concurrency level.

redis-benchmark -h 10.0.16.72 -p 8802 -n 90000000 -r 90000000 -t mset -P 1000 -c 100

You can benchmark the performance of the Redis SET command using the redis-benchmark utility. The following example demonstrates a high-load test configuration targeting a specific host and port with a large number of requests and parallel clients.

redis-benchmark -h 10.0.16.72 -p 8802 -n 90000000 -r 90000000 -t set -P 1000 -c 100

To benchmark the GET command performance in Redis, use the redis-benchmark utility. The following example demonstrates a high-load test configuration:

• -h: Target host IP
• -p: Target port
• -n: Total number of requests
• -r: Total number of requests (often used for range/repeat)
• -t: The specific command to benchmark (get)
• -P: Pipeline mode (number of requests to pipeline)
• -c: Number of parallel clients

Example command:

redis-benchmark -h 10.0.16.72 -p 8802 -n 90000000 -r 90000000 -t get -P 1000 -c 100

To start the Corvus proxy, execute the binary and provide the path to your configuration file as the first argument. An example configuration file is provided in the repository as corvus.conf.

./src/corvus path/to/corvus.conf

When running redis-benchmark for the set command, the following flags are used in the provided benchmark profile:

• -h <host>: The Redis server hostname or IP (e.g., 10.0.16.72).
• -p <port>: The Redis server port (e.g., 8802).
• -n <number>: Total number of requests to perform (e.g., 90000000).
• -r <repetitions>: Number of repetitions per key (e.g., 90000000).
• -t <type>: The command type to benchmark (e.g., set).
• -P <pipeline>: Number of requests to pipeline (e.g., 1000).
• -c <clients>: Number of parallel clients to use (e.g., 100).

To create a new server connection, use server_create(). This function requires a pointer to a context structure and an existing file descriptor (fd). It returns a pointer to a connection structure representing the new connection, or NULL if creation fails.

struct connection *conn = server_create(ctx, fd);