DEV Community

Ashish Sharda
Ashish Sharda

Posted on

Redis 8.6 is here: faster, smarter, and built for AI-era workloads

#redis #performance #backend #database

Redis 8.6

TL;DR: Redis 8.6 just went GA in open source. It brings more than 5× throughput over Redis 7.2, up to 35% lower latency on sorted sets, massive memory savings on hashes and sorted sets, production-grade Streams guarantees, hot key detection, smarter eviction, TLS auto-auth, and native NaN support in time series. Here's everything that matters.

Table of Contents

01 — The numbers: performance at a glance

Redis 8.6 isn't a quiet patch release. This is a generational performance leap. On a single node using 16 cores (ARM Graviton4), Redis 8.6 hits 3.5M ops/sec at pipeline size 16. That's more than 5× the throughput of Redis 7.2 on the same hardware.

Metric Improvement vs Redis 8.4
Sorted set commands latency ↓ 35%
GET latency (short strings) ↓ 15%
List commands latency ↓ 11%
Hash commands latency ↓ 7%
Sorted set memory footprint ↓ 30.5%
Hash memory footprint ↓ 16.7%
Vector insertion (VADD) ↑ 43%
Vector query performance ↑ 58%

Memory footprint improvements are just as notable: hashes shrink by up to 16.7%, sorted sets by up to 30.5%. That's real money saved on cloud infra.

💡 Benchmark context: Single node, 16 cores on an m8g.24xlarge (ARM Graviton4), 11 io-threads, pipeline size 16, 2000 clients, 1M keys, 1K string values, 1:10 SET:GET ratio.

02 — Streams: at-most-once production guarantee

Streams got a huge reliability upgrade. Redis 8.6 introduces idempotent production — a guarantee that a message will be added to a stream at most once, even when producers crash and retry.

This addresses a very real pain point in event-driven systems. When a producer sends a message, gets a network timeout, and retries — without this guarantee, you end up with duplicate events. Now Redis handles deduplication natively.

XADD mystream IDEM producer-id seq-123 * field value
Enter fullscreen mode Exit fullscreen mode

Combined with the 8.2 multi-group acknowledgment and 8.4's pending message recovery, Streams in Redis 8.6 are genuinely production-ready for financial systems, media pipelines, and AI inference queues.

03 — Hot key detection with HOTKEYS

One of the trickiest production scaling problems — hot keys — now has a native Redis command. The new HOTKEYS command lets you detect keys consuming disproportionate CPU or network resources in real time.

HOTKEYS
Enter fullscreen mode Exit fullscreen mode

This completes a trifecta of hot spot tooling across three releases:

Release Feature What it does
Redis 8.2 CLUSTER SLOT-STATS Detect hot slots across the cluster
Redis 8.4 Atomic Slot Migration Zero-downtime rebalancing of hot slots
Redis 8.6 HOTKEYS Pinpoint individual hot keys causing load

Together, these give you end-to-end cluster observability — from slot to individual key — without reaching for external profiling tools.

04 — New eviction policies for AI workloads

Redis has long had LRU (least recently used) eviction. Now 8.6 introduces two new eviction policies based on least recently modified (LRM) semantics:

  • allkeys-lrm — evict the least recently modified key across all keys
  • volatile-lrm — same, but only among keys with a TTL set

Why does this matter for AI? In AI inference pipelines, a key might be read frequently (LRU keeps it hot) but rarely updated. LRM lets you evict stale model outputs or embedding caches that are no longer being written to — exactly the behavior you want when managing inference result caches at scale.

⚠️ Tip: If you're on allkeys-lru and running AI inference caches, consider evaluating allkeys-lrm — you may see better cache hit rates and more predictable memory behavior.

05 — TLS auto-auth via certificate CN

This one is genuinely slick. Prior to 8.6, even with mutual TLS configured, clients still had to send an AUTH command at the application layer. Starting with 8.6, Redis can automatically authenticate mTLS clients based on the certificate's Common Name (CN).

tls-auth-clients yes
tls-client-cert-auth-user-prefix acl-user-
Enter fullscreen mode Exit fullscreen mode

Certificate possession becomes the sole credential. No more managing ACL passwords in your app config alongside TLS certs — the cert is the auth. This is huge for service mesh deployments and zero-trust architectures.

06 — NaN support in time series

Redis time series now supports NaN (Not a Number) values as a first-class way to represent missing measurements. Previously, teams used sentinel values like -1 or 0 which would corrupt aggregations.

TS.ADD sensor:temp 1714500000 NaN
TS.ADD sensor:temp 1714503600 23.4
Enter fullscreen mode Exit fullscreen mode

Now you can mark a data point as "unavailable at collection time" and fill it in later, without breaking range queries or aggregations. Critical for telemetry pipelines, observability stacks, and financial data collection where gaps are expected.

07 — How to upgrade

Version Status Available in
8.6 ✅ GA Redis Open Source now; Cloud/Software soon
8.4 ✅ GA Redis Cloud (Essentials & Pro)
8.8 🔶 M02 preview Docker Hub (not for production)

Pull Redis 8.6 via Docker:

docker pull redis:8.6
docker run -d --name redis86 -p 6379:6379 redis:8.6
Enter fullscreen mode Exit fullscreen mode

Or grab it from redis.io/downloads. The release is backward compatible — a standard rolling upgrade applies for most configurations.

📦 If you're on Redis Cloud, 8.4 is already rolling out to Essentials and Pro. Redis 8.6 will follow into Cloud and Redis Software in upcoming releases. No action needed on managed offerings.

Redis 8.6 is one of the more meaningful releases in recent memory. The throughput and latency numbers are genuinely exciting, and the operational improvements — HOTKEYS, mTLS auto-auth, LRM eviction, Streams idempotency — close gaps that have been friction points for production teams for years. If you're running Redis in anger, this one is worth the upgrade.

Sources: Redis 8.6 announcement blog · What's new in two — March 2026

Top comments (0)