gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

Updated Filer Benchmark (markdown)

Chris Lu 2020-07-12 15:32:47 -07:00
parent 3a529322f8
commit 5c766b9b40
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
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.