开发者在Hacker News发布了KiviDB,一款从2026年2月开始开发的开源Redis兼容内存数据库项目1。该项目支持RESP2和RESP3协议、具备向量缓存功能,核心引擎采用AGPLv3许可证1,并已在GitHub开源,同时提供AWS、GCP和Azure三大云平台的管理服务1。
在性能对比中,KiviDB表现出明显优势1。基准测试使用2台c7gn.metal服务器、10M键、每键100字节的配置运行1。管道化GET操作方面,KiviDB达到21.2M ops/sec,相比Dragonfly 2.0的9.1M ops/sec和Redis 8.10的2.4M ops/sec均有显著提升,32分片Redis Cluster也仅达4.7M ops/sec1。但在非管道化GET性能上,Dragonfly以3.35M ops/sec领先KiviDB的3.07M ops/sec1。内存开销方面,KiviDB每键占用177B,介于Dragonfly的134B和Redis的178B之间1。该项目的Redis命令兼容度约为98-99%1。
Developers have unveiled KiviDB, a Redis-compatible in-memory database project that began development in February 2026, featuring support for both RESP2 and RESP3 protocols along with vector caching capabilities 1. The project has been open-sourced on GitHub and offers cloud management services, with its core engine licensed under AGPLv3 1.
Performance benchmarks demonstrate significant advantages over competing solutions 1. In pipelined GET operations, KiviDB achieved 21.2 million operations per second, substantially outperforming Dragonfly 2.0's 9.1 million ops/sec and Redis 8.10's 2.4 million ops/sec, while Redis Cluster with 32 shards reached 4.7 million ops/sec 1. For non-pipelined GET operations, Dragonfly led with 3.35 million ops/sec compared to KiviDB's 3.07 million ops/sec 1. The tests were conducted on two c7gn.metal servers with 10 million keys of 100 bytes each across 32 cores 1. In terms of memory overhead per key, KiviDB required 177 bytes compared to Dragonfly's 134 bytes and Redis's 178 bytes 1.
KiviDB maintains approximately 98-99% compatibility with Redis commands 1 and supports deployment across major cloud platforms including AWS, GCP, and Azure 1. The project is available at https://kividb.io with source code accessible at https://github.com/kividbio/kividb 1.
评论
还没有评论,欢迎留下第一条。