Keydb Eng [2021]

Currently, KeyDB keeps all data in RAM. While Flash storage is supported via enable-flash , this feature introduces Automatic Data Tiering . It automatically moves "cold" (infrequently accessed) keys from RAM to a secondary storage layer (SSD/Disk) while keeping "hot" keys in memory. This allows KeyDB to hold datasets much larger than the available RAM without manual intervention from the application layer.

You can use keydb-cli with the --pipe option to import large amounts of data efficiently. keydb eng

io-threads 6 io-threads-do-reads yes

// 2. Submit async I/O job to the Tiering Thread Pool TieringJob *job = createTieringFetchJob(c->db, c->key); submitToBackgroundQueue(job); Currently, KeyDB keeps all data in RAM

// 2. Update stats (cache hits/misses) server.stat_tiering_loads++; keydb eng