> > > For object gateway, the performance is got by `swift-bench -t 64` which > uses 64 threads concurrently. Will the radosgw and http overhead be so > significant (94.5MB/s to 26MB/s for cluster1) when multiple threads are > used? Thanks in advance! > > Can't say what it "must" be, but if I log in to one of my rgw's (we have several, loadbalanced) and run ceph benchmarks against spindrive pools (ie, talking ceph directly), I get something like 200MB/s, if I run a write test on the same host, but talking s3-over-http against itself, I get something like 100MB/s, so the overhead in my case seems to be 100% (or 50% however you calculate it). You know there has to be some kind of penalty for doing protocol translations, if for nothing else, because of object store client does checksums, asks rgw to store it, rgw checksums the part(s), asks ceph to store, ceph sends ack, rgw sends ack to client with checksum and client compares before moving to next part. This will be far slower than just plain writes to ceph (the two innermost ops), and can in part be offset by using large IO, parallel streams, multiple rgw backends and so on. -- May the most significant bit of your life be positive. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |