From 58c9aef9cebab22cc39d5d13f82477d0519fb072 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Tue, 3 Mar 2020 09:36:54 -0800 Subject: [PATCH] Updated FAQ (markdown) --- FAQ.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index 8a46ce6..9dcea2a 100644 --- a/FAQ.md +++ b/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: