Databases 3 min read

Overview of Pika 3.0 New Features

Pika 3.0, a C++ open‑source Redis‑compatible storage built on RocksDB, introduces a new blackwidow engine, an improved binlog system, and a more efficient server layer, delivering higher performance, reduced disk usage, extended key length limits, and full Redis ZSET compatibility.

360 Tech Engineering
360 Tech Engineering
360 Tech Engineering
Overview of Pika 3.0 New Features

Pika is a popular 360 open‑source C++ project that implements a Redis‑compatible key‑value store on top of RocksDB, aiming to solve Redis’s high synchronization cost, slow recovery, single‑thread fragility, and high memory usage in large‑scale scenarios.

Pika 3.0 Main New Features

1. New Engine blackwidow

• Multiple interfaces see significant performance improvements.

• The new engine occupies less disk space for the same data.

• Key length limits for many data structures are no longer constrained to 256 bytes.

• ZSET structure provides the same precision as Redis.

2. New binlog (write2file)

• Higher parsing efficiency.

• Smaller size, more friendly to disk space.

• Supports multiple version formats with backward compatibility, eliminating upgrade hassles.

3. More Efficient Server Layer

• Optimized call efficiency between server and engine layers.

• Redundant code removed and logic refined for overall performance gains.

• Server code is now easier to read, though still not poetic.

Appendix

blackwidow storage format analysis: http://t.cn/Re8d2wT

Pika 3.0 upgrade process: http://t.cn/Re8dCzJ

Pika differentiated management commands: http://t.cn/Re8dnS2

Pika change log: http://t.cn/Re8gKxG

For more details, click “Read the original article”.

performanceRedisRocksDBPikaKey-Value Storedatabase engine
360 Tech Engineering
Written by

360 Tech Engineering

Official tech channel of 360, building the most professional technology aggregation platform for the brand.

0 followers
Reader feedback

How this landed with the community

login 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.