Why Is Redis So Fast? Unveiling the Secrets Behind Its Single‑Threaded Speed

1. Introduction

Almost every Java‑related interview asks about caching, covering basics like the 80/20 rule, hot vs. cold data, and advanced topics such as cache avalanche, penetration, warm‑up, update, and degradation. The most common cache servers are Redis and Memcached, with Redis being the focus here.

If you have never been asked why Redis is single‑threaded or why it is so fast, this article is a lucky find; interviewers can also use these questions to test candidates.

2. Redis Overview

Redis is an open‑source, in‑memory data‑structure store that can serve as a database, cache, and message broker.

It supports strings, hashes, lists, sets, sorted sets (ZSet), bitmaps, HyperLogLog, and geospatial indexes; the most common structures are String, List, Set, Hash, and ZSet.

Redis includes replication, Lua scripting, LRU eviction, transactions, and various persistence levels, and offers high availability via Sentinel and Cluster.

Persistence can be snapshotting or AOF; users may also disable persistence to use Redis purely as a fast network cache.

Redis stores data in memory, avoiding disk I/O bottlenecks, which makes read/write operations extremely fast.

Images illustrating disk‑based vs. memory‑based databases are shown.

3. How Fast Is Redis

Redis is a single‑process, single‑threaded KV database written in C, capable of exceeding 100,000 QPS in benchmarks, comparable to multi‑threaded in‑memory stores like Memcached.

Benchmark graphs demonstrate the magnitude of its performance.

4. Why Redis Is Fast

Entirely memory‑based, providing O(1) access similar to a HashMap.

Simple, purpose‑built data structures.

Single‑threaded design eliminates context switches, lock contention, and deadlock overhead.

Uses non‑blocking, multiplexed I/O (select/poll/epoll).

Implements its own VM to reduce system‑call overhead.

The article then explains the multiplexed I/O model, where a single thread monitors many connections and processes ready events efficiently.

5. Why Redis Is Single‑Threaded

Because Redis operations are memory‑bound, CPU is rarely the bottleneck; the limiting factors are memory size and network bandwidth, making a single‑threaded model sufficient and simpler.

Note that the server does spawn additional threads or processes for tasks like persistence, and since Redis 4.0 some operations can use multiple threads.

Images show Redis process threads and illustrate the warning that the “single‑threaded” claim applies only to network request handling.

6. Extensions

Additional models to be aware of for interviews:

Single‑process, multi‑threaded: MySQL, Memcached, Oracle (Windows).

Multi‑process: Oracle (Linux).

Nginx master‑worker architecture with both single‑process and multi‑process launch modes.

Images depict the Nginx process model.