gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated FAQ (markdown)

Chris Lu 2020-03-24 18:57:46 -07:00
parent 18402076e3
commit da7f1754f5
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
FAQ.md

@ -22,7 +22,7 @@ Yes.
* **SSD friendly**: SeaweedFS data is all append-only and create less stress to the disks, especially SSDs with a limited number of write cycles. SeaweedFS can maximumly reduce writes to the same SSD cell, thus increase its lifespan.
* **Bitrot Protection**:Entries on volume servers are CRC checked for any possible changes on server side and accessible via Etag. For Filer and S3 APIs, the files are also checked via MD5 Etag.
* **Bitrot Protection**: Entries on volume servers are CRC checked for any possible changes on server side and accessible via Etag. For Filer and S3 APIs, the files are also checked via MD5 Etag.
* **Replication**: Each file can have its own replication strategy. Erasure encoding not only saves space, but also can tolerate loss of 4 shards of data.
@ -34,7 +34,9 @@ Yes.
### How is it optimized for small files? How small is small files?
Optimization for small files is actually optimization for large amount of files. The file size does not matter. Filer server would chunk the files.
Optimization for small files is actually optimization for large amount of files. The file size does not matter.
Filer server would automatically chunk the files if necessary.
### Does it support large files, e.g., 500M ~ 10G?
Large file will be automatically split into chunks, in `weed filer`, `weed mount`, `weed filer.copy`, etc.