From 0b93a1ec64a94d33cc4408369430bfc27854e838 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Wed, 13 Jan 2021 12:05:12 -0800 Subject: [PATCH] Updated Filer as a Key Large Value Store (markdown) --- Filer-as-a-Key-Large-Value-Store.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Filer-as-a-Key-Large-Value-Store.md b/Filer-as-a-Key-Large-Value-Store.md index 1416edc..2b09f8f 100644 --- a/Filer-as-a-Key-Large-Value-Store.md +++ b/Filer-as-a-Key-Large-Value-Store.md @@ -14,7 +14,7 @@ With SeaweedFS, a large value can be stored as a chunk on volume servers and can There are two tricks: * Configure for [[Super Large Directories]]. It will avoid the additional work to maintain the file list in the large folder. -* Optionally configure to store small values in filer store. E.g., `weed filer -cacheToFilerLimit=1024` will store values less than 1KB to filer store itself. Accessing these entries are basically no difference than accessing the underlying key-value stores directly. +* Optionally configure to store small values in filer store. E.g., `weed filer -saveToFilerLimit=1024` will store values less than 1KB to filer store itself. Accessing these entries are basically no difference than accessing the underlying key-value stores directly. ## AWS S3 is a poor key-value store