mirror of
https://github.com/deepseek-ai/3FS.git
synced 2026-11-05 00:47:47 +00:00
[GH-ISSUE #76] How does 3FS support kvcache with high performance? #41
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/3FS#41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @walsonyang on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/76
What's the difference between 3FS and RocksDB?Seems that 3FS use Foundation DB to store KV, and RocksDB supports SSD too.
So, in the scenario of KVCache for inference, why is 3FS needed?
@clicx commented on GitHub (Mar 5, 2025):
I have similar questions, why 3fs uses FoundationDB, LevelDB and RocksDB, they are working as the same functions.
@xiaoyao9933 commented on GitHub (Mar 5, 2025):
from
github.com/deepseek-ai/3FS@a3f0380a30/src/lib/api/hf3fs_expected.h (L53), it seems 3fs was developed as early as year 2014. Maybe its initial motivation is for quantitative trading, not for AI.