Github-Mirror/seaweedfs
1
0 Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2026-11-04 02:57:44 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated Filer Benchmark (markdown)

Chris Lu committed 2020-07-12 15:49:33 -07:00
1 parent ec7b2685e0
commit 06a173e6d3
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
Filer-Benchmark.md
+1 -1
@@ -18,7 +18,7 @@ So not only it is fairly slow, but also it is expensive to use S3 as a key-value
## SeaweedFS with YCSB
### SeaweedFS Benefits
However, still, wouldn't it be nice that you can use an unlimited disk spaces to quickly store and access files? This way, only a file name is needed to store in the main databases, which costs more for storage?
The databases usually is much more expensive than SeaweedFS for the same capacity. It would be nice to to quickly store and access files with unlimited disk space, and only store a file name in the main database.
SeaweedFS has no additional cost for API access, as long as you setup the SeaweedFS cluster. For example, it is a fixed monthly cost if running on EC2 instances. You do not need to worry about unmanageable API costs.