mirror of
https://github.com/deepseek-ai/3FS.git
synced 2026-11-05 00:47:47 +00:00
[GH-ISSUE #102] Why are file chunks stored in the local file system rather than directly on the raw disk? #58
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#58
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 @hit1943 on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/102
I noticed that the file chunks are actually written to the local disk as data blocks, and rocksdb can be used as an index and metadata storage for the file chunks. So, is it still necessary to use the local file system? As an analogy, ceph uses bluestore to manage raw disks.
@SF-Zhou commented on GitHub (Mar 5, 2025):
In our scenario, the combination of NVMe + XFS + AIO can meet the read/write performance requirements. Directly managing raw disks may provide certain performance benefits, but it also increases the complexity of development and maintenance.