Why RedisJSON Outperforms MongoDB and ElasticSearch in Real‑World Benchmarks
A comprehensive performance benchmark shows RedisJSON delivering dramatically higher throughput and lower latency than MongoDB and ElasticSearch across isolated writes, isolated reads, and mixed workloads, highlighting its superior scalability and stability for modern data‑intensive applications.
Overview
Recent official performance tests show that RedisJSON (RedisSearch) dramatically outperforms MongoDB and ElasticSearch. For isolated writes RedisJSON is 5.4× faster than MongoDB and over 200× faster than ElasticSearch; for isolated reads it is 12.7× faster than MongoDB and over 500× faster than ElasticSearch.
In mixed workloads, RedisJSON maintains stable search and read performance while ElasticSearch degrades.
RedisJSON delivers roughly 50× higher operations per second than MongoDB and 7× higher than ElasticSearch, with latency up to 90× lower.
Query Engine
The RedisJSON development emphasizes performance. Version 2.2 improves load and query speed by 1.7× over 2.0, and also reduces throughput latency.
2.1 Load Optimization
Benchmark results from the New York City taxi dataset show consistent performance gains across each new RedisJSON release.
2.2 Full‑Text Search Optimization
Indexing 5.9 million Wikipedia abstracts and running full‑text queries demonstrates substantial improvements in write, read, and search latency from v2.0 to v2.2.
Comparison with Other Frameworks
RedisJSON was benchmarked against MongoDB 5.0.3 and ElasticSearch 7.15 using the YCSB suite on identical AWS m5d.8xlarge clusters (one client + three database nodes). Tests covered pure CRUD, mixed read/write/search, and latency analysis.
3.1 Benchmark Setup
MongoDB 5.0.3: three‑member replica set with text index. ElasticSearch 7.15: 15 shards, query cache enabled, RAID‑0 on local NVMe SSDs. RedisJSON*: RediSearch 2.2 + RedisJSON 2.0 on OSS Redis Cluster v6.2.6 with 27 shards across three nodes.
3.2 100 % Write Benchmark
RedisJSON* ingests data 8.8× faster than ElasticSearch and 1.8× faster than MongoDB, while keeping sub‑millisecond latency; 99 % of requests complete within 1.5 ms.
3.3 100 % Read Benchmark
RedisJSON reads 15.8× more operations than ElasticSearch and 2.8× more than MongoDB, maintaining sub‑millisecond latency across the entire range.
3.4 Mixed Read/Write/Search Benchmark
In a realistic 65 % search / 35 % read workload, RedisJSON* sustains throughput while ElasticSearch degrades as write ratio increases. RedisJSON* achieves up to 16 K ops/sec versus 424 ops/sec for MongoDB.
3.5 Full Latency Analysis
Across all latency percentiles, RedisJSON* consistently stays in the sub‑millisecond range (p99 ≈ 0.23 ms), far ahead of MongoDB (≈ 5 ms) and ElasticSearch (≈ 10 ms). The advantage holds for reads, writes, and searches.
Architect's Alchemy Furnace
A comprehensive platform that combines Java development and architecture design, guaranteeing 100% original content. We explore the essence and philosophy of architecture and provide professional technical articles for aspiring architects.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
