From 85f68860ae3e050cad4bf42c8118b709e8ce191a Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Tue, 11 Jun 2019 10:15:26 -0700 Subject: [PATCH] Updated Erasure Coding for warm storage (markdown) --- Erasure-Coding-for-warm-storage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Erasure-Coding-for-warm-storage.md b/Erasure-Coding-for-warm-storage.md index db5c382..5041749 100644 --- a/Erasure-Coding-for-warm-storage.md +++ b/Erasure-Coding-for-warm-storage.md @@ -1,4 +1,4 @@ -This erasure coding implementation took some ideas from [f4: Facebook’s Warm BLOB Storage System](https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-muralidhar.pdf), without its high requirements. +This erasure coding implementation took some ideas from [f4: Facebook’s Warm BLOB Storage System](https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-muralidhar.pdf), without its high hardware requirements. Usually data is hot when it is fresh, and are accessed very often. SeaweedFS normal volumes tries hard to minimize the disk operations, but it comes with a cost of loading indexes in memory.