All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Srikanth Madugundi
	<srikanth.madugundi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ceph-users <ceph-users-Qp0mS5GaXlQ@public.gmane.org>
Subject: Re: radosgw + civetweb latency issue on Hammer
Date: Thu, 06 Aug 2015 10:51:14 -0500	[thread overview]
Message-ID: <55C38272.2090703@redhat.com> (raw)
In-Reply-To: <CACAg-u97BjhmGbjRogKzmyTL_iPzj9C0qAbEgF28-ONFqe5Drw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Srikanth,

Can you make a ticket on tracker.ceph.com for this?  We'd like to not 
loose track of it.

Thanks!
Mark

On 08/05/2015 07:01 PM, Srikanth Madugundi wrote:
> Hi,
>
> After upgrading to Hammer and moving from apache to civetweb. We
> started seeing high PUT latency in the order of 2 sec for every PUT
> request. The GET request lo
>
> Attaching the radosgw logs for a single request. The ceph.conf has the
> following configuration for civetweb.
>
> [client.radosgw.gateway]
> rgw frontends = civetweb port=5632
>
>
> Further investion reveled the call to get_data() at
> https://github.com/ceph/ceph/blob/hammer/src/rgw/rgw_op.cc#L1786 is
> taking 2 sec to respond. The cluster is running Hammer 94.2 release
>
> Did any one face this issue before? Is there some configuration I am missing?
>
> Regards
> Srikanth
>

  parent reply	other threads:[~2015-08-06 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06  0:01 radosgw + civetweb latency issue on Hammer Srikanth Madugundi
     [not found] ` <CACAg-u97BjhmGbjRogKzmyTL_iPzj9C0qAbEgF28-ONFqe5Drw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-06 15:51   ` Mark Nelson [this message]
2015-09-22  9:18   ` Giridhar Yasa
2015-09-22  9:19   ` Giridhar Yasa

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=55C38272.2090703@redhat.com \
    --to=mnelson-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    --cc=srikanth.madugundi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.