Hi Eric,
boost::beast is a low-level c++ http protocol library that's hosted at
https://github.com/boostorg/beast. Radosgw uses this library, along with
boost::asio, as the basis for its 'beast frontend'. The motivation
behind this frontend is its flexible threading model and support for
asynchronous networking. The civetweb server's thread-per-connection
model has been a major limitation for scalability. With ongoing work to
extend the asynchrony of the beast frontend into radosgw's request
processing, it'll be able to handle more concurrent requests with fewer
thread/memory resources than civetweb.
In nautilus though, the beast frontend still has this
thread-per-connection limitation, and its performance is comparable to
civetweb's. I expect we'll make more noise about it once we're further
along with the async refactoring and start to show the real wins. I hope
that helps to clarify the situation!
Casey
On 9/11/19 12:56 PM, Eric Choi wrote:
Replying to my own question:
2. Beast is not a web front end, so it would be an apple-to-orange
comparison. I just couldn't find any blogs / docs about it at first
(found it here: https://github.com/ceph/Beast)
Still unsure about the first question..
On Tue, Sep 10, 2019 at 4:45 PM Eric Choi <echoi@xxxxxxxxxx
<mailto:echoi@xxxxxxxxxx>> wrote:
Hi there, we have been using ceph for a few years now, it's only
now that I've noticed we have been using the same name for all RGW
hosts, resulting when you run ceph -s:
rgw: 1 daemon active (..)
despite having more than 10 RGW hosts.
* What are the side effects of doing this? Is this a no-no? I can
see the metrics can (ceph daemon ... perf dump) be wrong, are the
metrics kept track independently (per host)?
* My second question (maybe this should be a separate email!) is
that comparison between Beast vs Civetweb. We only recently
upgraded to Nautilus, so Beast became available as an option to
us. I couldn't find any blogs / docs on comparing these 2
frontends. Is there any recommended reading or could someone give
me an overview?
Much appreciated!
--
Eric Choi
Senior Software Engineer 2 | Core Platform
--
Eric Choi
Senior Software Engineer 2 | Core Platform
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
