From 5c766b9b4032c44d598485138d0934cd95823b10 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Sun, 12 Jul 2020 15:32:47 -0700 Subject: [PATCH] Updated Filer Benchmark (markdown) --- Filer-Benchmark.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Filer-Benchmark.md b/Filer-Benchmark.md index e69eb85..ad99c08 100644 --- a/Filer-Benchmark.md +++ b/Filer-Benchmark.md @@ -10,7 +10,7 @@ But after digging deeper into it, I found the S3 is poorly implemented and not m What is more, the API cost is a big concern. S3 seems cheap for storage, but for small objects which requires frequent access, the API cost can quickly add up at $0.005 for 1 thousand PUT/DELETE requests. If we need to test with 1 million objects: - * 1 million write operations cost $5, or $150/month for 12 operations/second. + * 1 million write operations cost $5, or $150/month for 12 operations/second in production. * Another $5 to clean up the 1 million test objects. So not only it is fairly slow, but also it is expensive to use S3 as a key-value store.