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-03 09:36:54 -08:00
parent 243e186c1f
commit 58c9aef9ce
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
FAQ.md

@ -18,6 +18,10 @@ The internal management APIs are in gRPC. You can generate the language bindings
### Does it support FUSE?
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.
### Does it support large files, e.g., 500M ~ 10G?
Large file will be automatically split into chunks, in `weed filer`, `weed mount`, etc.
@ -52,7 +56,7 @@ See #100 https://github.com/chrislusf/seaweedfs/issues/100
### How to store large logs?
The log files are usually very large. But SeaweedFS is mostly for small-to-medium large files. How to store them? "weed filer" can help.
The log files are usually very large. Use `weed filer` to store them.
Usually the logs are collected during a long period of time span. Let's say each day's log is about a manageable 128MB. You can store each day's log via "weed filer" under "/logs/" folder. For example: