Redis: Cleaning Up the Core Before 8.10

Redis maintainers spent the day tightening up internals ahead of the 8.10 release cycle — fixing memory accounting, simplifying dictionary iteration, and clarifying build documentation. Module updates for JSON and Bloom also landed, rounding out a housekeeping-focused stretch of work.

Duration: PT2M30S

Episode overview

This episode is a short developer briefing from Redis.

It explains recent repository work in plain language.

  • Show: Redis
  • Published: 2026-07-15T13:13:04Z
  • Audio duration: PT2M30S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good day, and welcome to Redis, your developer briefing for July 15th, 2026.

Today's activity centers on one clear theme: getting the internals right before the 8.10 release ships more widely.

Start with memory accuracy. PR 15462, from fcostaoliveira, fixes a real over-counting bug in dict memory usage. When Redis stores sets, hashes, or sorted-set indexes without values — an optimization called "no value" — the memory tracker was still charging the full entry size, inflating what "memory usage" reports…

Second theme: simplifying core code for maintainability. Moti Cohen's PR 15437 removes the "dict for each" macro from the dictionary header. It was used in just two places, both in the module system's defrag start and stop functions, and it diverged from the standard iterator pattern used nearly 300 times elsewhere…

Third theme: build and release documentation catching up to reality. PR 15454 updates the build-from-source guide for Redis 8.10 and later, reflecting that release tarballs now bundle module config, and specifying exact Rust and LLVM versions needed for RediSearch's link-time optimization. The companion commit also…

Separately, PR 15463 bumps the JSON and Bloom modules to…

Nearby episodes from Redis

  1. Build Environment Cleanup
  2. Storage Overhauls and a Security Patch
  3. Correctness Fixes and a Module Refresh
  4. Correctness Under Concurrency
  5. Replication Under Load Gets a Fix
  6. Edge Cases in Numeric Boundaries
  7. Weekly Recap - Security Fixes, Crash Hardening, and the Modules Build Overhaul
  8. Correctness Fixes Under the Hood