diff options
| author | Chris Lu <chrislusf@users.noreply.github.com> | 2020-03-24 22:11:23 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-24 22:11:23 -0700 |
| commit | 0dbaa70af263d2645fa7fef7d884158c2fa2eb59 (patch) | |
| tree | 61b52f6193ee9cf1ab65d094b2082979fa8c5725 | |
| parent | e63a79ade842df4bcd0ec0096229028236215ae1 (diff) | |
| download | seaweedfs-0dbaa70af263d2645fa7fef7d884158c2fa2eb59.tar.xz seaweedfs-0dbaa70af263d2645fa7fef7d884158c2fa2eb59.zip | |
Update README.md
| -rw-r--r-- | README.md | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -381,6 +381,14 @@ GlusterFS hashes the path and filename into ids, and assigned to virtual volumes [Back to TOC](#table-of-contents) +### Compared to MooseFS ### + +MooseFS choose to neglect small file issue. From moosefs 3.0 manual, "even a small file will occupy 64KiB plus additionally 4KiB of checksums and 1KiB for the header", because it "was initially designed for keeping large amounts (like several thousands) of very big files" + +MooseFS Master Server keeps all meta data in memory. Same issue as HDFS namenode. + +[Back to TOC](#table-of-contents) + ### Compared to Ceph ### Ceph can be setup similar to SeaweedFS as a key->blob store. It is much more complicated, with the need to support layers on top of it. [Here is a more detailed comparison](https://github.com/chrislusf/seaweedfs/issues/120) |