Replies: 5 comments 12 replies
-
|
Thanks for your thorough work, it's really helpful for my selection! |
Beta Was this translation helpful? Give feedback.
-
|
This is error logs
|
Beta Was this translation helpful? Give feedback.
-
|
Hello @xpnuo , Thank you for your feedback. The bug related to 512 threads with 1M has been resolved. You can find the fix here: 0927f93 Regarding your stress test results, 12 MiB/s seems incredibly low—we find that hard to believe. For reference, even on a minimal setup with 2 cores and 2GB RAM, we are able to reach 8 MiB/s. We will conduct further testing on our end. In the meantime, could you please let us know what your disk IOPS is? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for sharing these benchmark results, very interesting work! Could you share more details on what is limiting the GET bandwidth? Thanks! |
Beta Was this translation helpful? Give feedback.















Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hardware resources:
Test object version:
Deployment method: All are deployed in a cluster, running on node{1...4}
Benchmark commend: ./warp mixed --host node1,node2,node3,node4 --access-key --secret-key --duration=1m --obj.size <> --concurrent <>
RustFS GET
RustFS PUT
SeaweedFS GET
SeaweedFS PUT
MinIO GET
MinIO PUT
Summarize
Based on the results:
Small files: seaweedfs > minio > rustfs
Large files: minio > rustfs > seaweedfs
It's possible that the rustfs cluster mode is not yet mature enough, and it may crash during load testing (almost certainly reproducible) with 512 threads and a file size of 1 MiB.
I'm really looking forward to the development of RustFS. Its architecture is almost identical to Minio (which later replaced Minio and provided a great solution—and its performance is comparable to Minio for large files).
Beta Was this translation helpful? Give feedback.
All reactions