Right now attempting to benchmark the database using the redis-benchmark CLI tool results in failure. I do not know why the aforementioned tool fails to benchmark Thesaurus. My intuition tells me that redis-benchmark sends commands that Thesaurus does not yet support. The logs hint at this:
[2026-06-04T21:33:06Z WARN thesaurus::handler] Handler d5876a19-ae32-4200-87c0-95d0c19b413b decode error: unknown RESP2 prefix: 'P'
[2026-06-04T21:33:06Z WARN thesaurus] Error while running task at socket 127.0.0.1:54690
unknown RESP2 prefix: 'P'
Proposed solution
Create a script that persists everything redis-benchmark transmits with the help of a TCP listener (bind to 127.0.0.1, port 6379). After that, we will have a clearer understanding on how to use redis-benchmark with Thesaurus.
Alternatives considered
Find a different way, other than the redis-benchmark CLI tool, to benchmark Thesaurus.
Scope
This issue does not propose any changes to the codebase; it is meant for investigation and discussion.
Right now attempting to benchmark the database using the
redis-benchmarkCLI tool results in failure. I do not know why the aforementioned tool fails to benchmark Thesaurus. My intuition tells me thatredis-benchmarksends commands that Thesaurus does not yet support. The logs hint at this:Proposed solution
Create a script that persists everything
redis-benchmarktransmits with the help of a TCP listener (bind to127.0.0.1, port6379). After that, we will have a clearer understanding on how to useredis-benchmarkwith Thesaurus.Alternatives considered
Find a different way, other than the
redis-benchmarkCLI tool, to benchmark Thesaurus.Scope
This issue does not propose any changes to the codebase; it is meant for investigation and discussion.