Databases 5 min read

Redisun 1.4.0: A 33KB Java Redis Client That Beats Redisson by 8×

Redisun 1.4.0 is a 33KB Java Redis client that uses connection‑reuse and Java AIO to achieve up to ten‑fold higher throughput than traditional clients such as Redisson, Lettuce and Jedis, while reducing startup time, memory usage, image size and bandwidth, and it offers a simple Maven dependency and API.

Three Knives
Three Knives
Three Knives
Redisun 1.4.0: A 33KB Java Redis Client That Beats Redisson by 8×

Why Redisun Matters

Redisun 1.4.0 is a lightweight Redis client built on smart‑socket, targeting Java developers who need maximum performance.

Size Comparison

Redisun: 33KB (≈ a high‑resolution image)

Lettuce: ~2 MB (≈ 60 Redisun)

Jedis: ~500 KB (≈ 15 Redisun)

Redisson: 1.8 MB+ (≈ 55 Redisun)

Smaller JAR size translates into faster startup, lower memory consumption, smaller container images and reduced bandwidth.

Performance Numbers

Asynchronous Operations

Redisun:  ████████████████████████████████████████ 485,000 OPS
Redisson: ███ 50,000 OPS
Lettuce:  ███ 60,000 OPS

Redisun is 8× Lettuce and 9.7× Redisson.

Synchronous Operations

Redisun:  ████████████████████ 76,000 OPS
Lettuce:  ████ 30,000 OPS
Jedis:    ████ 25,000 OPS
Redisson: ████ 28,000 OPS

Redisun leads other clients by 2–3×.
Real‑world impact: Same hardware can handle 8× more concurrent requests. QPS can cut server costs by up to 80%. Same latency requirements can be met with fewer resources.

Core Technical Secrets

Connection Reuse

Traditional clients wait for a response per request. Redisun’s connection‑reuse allows a single TCP connection to process multiple concurrent requests in parallel.

Traditional: [Req1] → wait → [Resp1] → [Req2] → wait → [Resp2]
Redisun:    [Req1] → [Req2] → [Req3] → [Resp1] → [Resp2] → [Resp3]
            ↑ parallel processing, no waiting

Result: throughput improves 5–10×.

Java AIO Optimizations

Zero‑blocking I/O – fully leverages OS asynchronous capabilities.

Zero‑thread waste – a single thread handles tens of thousands of concurrent connections.

Zero‑copy transfer – reduces data copying, lowering CPU usage.

Three‑Minute Get‑Started Guide

1. Add Maven Dependency

<dependency>
    <groupId>tech.smartboot</groupId>
    <artifactId>redisun</artifactId>
    <version>1.4.0</version>
</dependency>

2. Write Code

import tech.smartboot.redisun.Redisun;

Redisun redisun = Redisun.create(options ->
    options.setAddress("127.0.0.1:6379")
);

redisun.set("user:1001", "Alice");
String user = redisun.get("user:1001");
redisun.close();

3. Enjoy Lightning Speed

The client starts instantly and delivers high‑throughput operations.

v1.4.0 Updates

Underlying smart‑socket upgraded to 2.0.0 – API unchanged, seamless upgrade.

Ecosystem sync – follows upstream framework evolution.

Stability – maintains consistent reliability.

Community & Resources

Open‑source projects thrive with community support.

Related links: GitHub repository: https://github.com/smartboot/redisun Official documentation: https://smartboot.tech/redisun smart‑socket: https://github.com/smartboot/smart-socket

Redisun: small, fast, and stable – redefining Redis client performance with just 33KB.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

JavaRedisPerformance benchmarkingAIOConnection reuseRedis client
Three Knives
Written by

Three Knives

Every line of code you contribute to open source could help make the future better.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.