From dc35e4d53aca54c6eb278e0d38ca95fd75386430 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Tue, 29 Dec 2020 03:13:54 -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 3c02d06..0178656 100644 --- a/Filer-as-a-Key-Large-Value-Store.md +++ b/Filer-as-a-Key-Large-Value-Store.md @@ -4,7 +4,7 @@ Usually key-value stores are limited by the storage capacity. As the data size g Instead, we can move the large value data outside of KV stores, and only store the reference in KV stores. -With SeaweedFS, a large value can be stored as a chunk on volume servers and can be referenced by a chunk id, which is 20 bytes. In addition, the smaller values can be stored directly in KV stores, saving one network hop. So you can get an efficient KV store with almost unlimited size, while still have the same access speed for small values and reasonable speed for larger values. +With SeaweedFS, a large value can be stored as a chunk on volume servers and can be referenced by a chunk id, which is 16 bytes. In addition, the smaller values can be stored directly in KV stores, saving one network hop. So you can get an efficient KV store with almost unlimited size, while still have the same access speed for small values and reasonable speed for larger values. ## How to do it?