January 2026 Summaries

Valkey 9.0 introduces significant improvements to handle large data objects in multi-tenant systems without compromising the performance of small object requests, a problem that plagued Valkey 8.1 due to blocking caused by large object fetches. The new version utilizes a reply copy avoidance mechanism, allowing the I/O threads to handle data transfers by passing a pointer reference instead of copying large objects into reply buffers, thereby avoiding the main thread blocking that previously disrupted smaller requests. This innovation ensures consistent performance even with mixed workloads, as evidenced by maintaining low latency for small objects while large data transfers occur. Additionally, the optimization can be configured via three hidden settings, providing further tuning flexibility if needed, although the default settings are suitable for most use cases. This change is part of a series of community-driven enhancements that collectively improve Valkey's efficiency, and future updates promise to further optimize the system's handling of cache workloads by offloading read commands entirely to worker threads.

Valkey 9.0 introduces a significant performance improvement over its predecessor by implementing a feature called reply copy avoidance, which addresses the adverse impact of handling large objects on system performance. In Valkey 8.1, fetching large objects such as 10MB blobs led to increased latency and degraded the performance of systems serving smaller objects due to the main thread being blocked on memory copy operations. By contrast, Valkey 9.0 minimizes this issue by using pointer references instead of copying large data, allowing the I/O threads to handle data transfer more efficiently without blocking the main thread. This change ensures that large object traffic has minimal impact on small object workloads, maintaining low latency even in mixed environments. The optimization is controlled by configurations that are not included in the default settings, yet their default values are suitable for most scenarios. This feature is part of a series of community-driven enhancements aimed at optimizing cache performance, with future updates expected to further improve system efficiency.