Improve RESTORE REPLACE performance for new keys
Optimized RESTORE REPLACE command to use a single dictionary lookup instead of three when adding new keys, reducing overhead during dictionary rehashing operations.
For a new key, RESTORE REPLACE did three dict lookups (find, delete,
add). It now reuses the link from the first lookup for the insert and
skips the delete when no key is present, so it does a single lookup. The
impact is more visible while the dict is rehashing: three lookups would
trigger three incremental rehash steps instead of one. A similar
optimization could be applied to the non-REPLACE path, but RESTORE
REPLACE is the hotter path (e.g. atomic slot migration) and it would
require more changes.
Source: original entry ↗
More from Redis
Follow Redis to get its new changes in your feed and email digest.
Improve test timeout diagnostics with crash reports and stack traces
When a test times out, the system now collects crash reports from Redis servers and stack traces from clients before terminating, providing better diagnostics for hung tests instead of silently killing them.
Security fixes in Redis 8.10.2
This release addresses critical security vulnerabilities including ACL permission bypasses in transactions, unauthenticated cluster bus access, and server crashes in TimeSeries, RedisSearch, and Vector Sets. The new cluster-bus-port-protected-mode option allows nodes to require TLS authentication for cluster bus communication.
Redis 8.8.3 Security and Stability Release
This release includes critical security fixes for transaction ACL bypasses, cluster bus authentication warnings, and crash prevention in TimeSeries and Vector Sets. A new cluster-bus-port-protected-mode option allows nodes to enforce authentication on the cluster bus port.