From: Ken Dreyer <kdreyer@redhat.com>
To: ceph-devel@vger.kernel.org
Subject: Re: RGW's apache and mod_fastcgi
Date: Wed, 14 Jan 2015 18:40:21 -0700 [thread overview]
Message-ID: <54B71A85.8080807@redhat.com> (raw)
In-Reply-To: <54AC3429.2030104@redhat.com>
On 01/06/2015 12:14 PM, Ken Dreyer wrote:
> There's the question of Unix Domain Sockets support. In Yehuda's testing
> with mod_proxy_fcgi, Unix Domain Sockets (UDS) provide a lot better
> performance in comparison to TCP sockets. Apache's UDS support shipped
> in Apache upstream version 2.4.9, but both RHEL and Ubuntu have versions
> older than this. RHEL 7 has httpd 2.4.6, and Trusty has 2.4.7. My
> intention is to request that the Ubuntu apache2 maintainers to backport
> UDS to their Trusty package, similarly to what Red Hat intends to ship
> in RHEL 7.1.
To follow up on this: Apache's mod_proxy UDS support is now present in
the httpd-2.4.6-19 package in RHEL and CentOS. I've opened
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1411030 to
request the Ubuntu package maintainers backport UDS support for Trusty's
Apache 2.4.7 package.
- Ken
prev parent reply other threads:[~2015-01-15 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 19:14 RGW's apache and mod_fastcgi Ken Dreyer
2015-01-15 1:40 ` Ken Dreyer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54B71A85.8080807@redhat.com \
--to=kdreyer@redhat.com \
--cc=ceph-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox