Thank you very much. As you mentioned, connecting via URI is not currently supported, but it’s not difficult to implement, so I will consider adding it to the specification.
Solidis isn’t necessarily aiming to outperform ioredis or node-redis in every way — its primary goal is to reduce bundle size rather than maximize raw performance. That said, it does offer some performance advantages in practice. Solidis is designed to handle pipelined commands more efficiently within a single event loop iteration and parses responses in a more event-loop-friendly manner.
As a result, in most real-world scenarios, Solidis tends to be about 2–3x faster than ioredis (even with auto-pipelining enabled). Compared to node-redis, the performance is generally on par or slightly behind.
One caveat: if the payloads being parsed are very large, Solidis can experience increased latency due to its parser being more CPU-intensive, which may introduce delays compared to other stacks.
As a result, in most real-world scenarios, Solidis tends to be about 2–3x faster than ioredis (even with auto-pipelining enabled). Compared to node-redis, the performance is generally on par or slightly behind.
One caveat: if the payloads being parsed are very large, Solidis can experience increased latency due to its parser being more CPU-intensive, which may introduce delays compared to other stacks.