Hi, As part of characterizing RGW read performance, have observed that there is a single RADOS connection that is consumed by so many RGW worker threads, resulting in some amount of serialization at that level. Making the RADOS handles multiple, and shared across the worker threads in a RR fashion, have yielded a factor of ~50% improvement (for read requests) in throughput and with much better response times on my setup (will share the configuration and results in due course). Wanted to understand if there is a constraint in having single RADOS instance per RGW, that could otherwise be a configurable option, for which I have a PR in pipeline. Thanks, -Pavan. ________________________________ PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies). -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
