All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Bonvalet <ceph.list-PaEMFeTk6C1QFI55V6+gNQ@public.gmane.org>
To: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: ceph-users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>
Subject: Re: Performance problems
Date: Tue, 16 Apr 2013 09:02:10 +0200	[thread overview]
Message-ID: <1366095730.3018.31.camel@localhost> (raw)
In-Reply-To: <1365788736.32141.13.camel@localhost>



Le vendredi 12 avril 2013 à 19:45 +0200, Olivier Bonvalet a écrit :
> Le vendredi 12 avril 2013 à 10:04 -0500, Mark Nelson a écrit :
> > On 04/11/2013 07:25 PM, Ziemowit Pierzycki wrote:
> > > No, I'm not using RDMA in this configuration since this will eventually
> > > get deployed to production with 10G ethernet (yes RDMA is faster).  I
> > > would prefer Ceph because it has a storage drive built into OpenNebula
> > > which my company is using and as you mentioned individual drives.
> > >
> > > I'm not sure what the problem is but it appears to me that one of the
> > > hosts may be holding up the rest... with Ceph if the performance of one
> > > of the hosts is much faster than others could this potentially slow down
> > > the cluster to this level?
> > 
> > Definitely!  Even 1 slow OSD can cause dramatic slow downs.  This is 
> > because we (by default) try to distribute data evenly to every OSD in 
> > the cluster.  If even 1 OSD is really slow, it will accumulate more and 
> > more outstanding operations while all of the other OSDs complete their 
> > requests.  What will happen is that eventually you will have all of your 
> > outstanding operations waiting on that slow OSD, and all of the other 
> > OSDs will sit idle waiting for new requests.
> > 
> > If you know that some OSDs are permanently slower than others, you can 
> > re-weight them so that they receive fewer requests than the others which 
> > can mitigate this, but that isn't always an optimal solution.  Some 
> > times a slow OSD can be a sign of other hardware problems too.
> > 
> > Mark
> > 
> 
> and does response time of OSD are log somewhere, to identify that "weak
> link" ?
> 
> 

I think I found the answer with the admin socket :
    ceph --admin-daemon /var/run/ceph/ceph-osd.14.asok perf dump

For example in the output I can see op_latency, op_w_latency,
op_r_latency, op_rw_latency, etc. Great.


_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

       reply	other threads:[~2013-04-16  7:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOiTGHkvMLqj4KC3ehGD=pOO77+Hkxs2ao1PzPyfeMQ2L6P5rg@mail.gmail.com>
     [not found] ` <CAPYLRzioybviGrhN6CfoJh8sN1yPk2zi5khpQ+mzqTHoRRWCRg@mail.gmail.com>
     [not found]   ` <CAOiTGHnNrs5vki6Ht7ug6rLhBU6Uwm8+cN-JqpvHatbShC7qFA@mail.gmail.com>
     [not found]     ` <516322B2.2070103@inktank.com>
     [not found]       ` <CAOiTGHn_jeAwtK-jRGZL0zOgt7W8Tw_YVoWWwgXGpFvhMLQidg@mail.gmail.com>
     [not found]         ` <516336A6.5080806@inktank.com>
     [not found]           ` <CAOiTGH=iPdw_7RgHLoVFLC98c3Qy+XbOzLjVv0-e03MvEC8bCw@mail.gmail.com>
     [not found]             ` <5166AFD1.8070003@inktank.com>
     [not found]               ` <CAOiTGHmjW2EffvLjWqaHM+ObHNe+foURfXDXtEPTXSMiz6J_Wg@mail.gmail.com>
     [not found]                 ` <5168229A.10002@inktank.com>
     [not found]                   ` <1365788736.32141.13.camel@localhost>
2013-04-16  7:02                     ` Olivier Bonvalet [this message]
2007-10-26 23:33 Performance problems Boscovich, Maximiliano
2007-10-27  9:01 ` Frantisek Hanzlik
2007-10-27 18:19 ` Frank Cox
2007-10-28 21:21   ` Frank Cox
2007-11-06 15:40     ` Boscovich, Maximiliano
  -- strict thread matches above, loose matches on Subject: below --
2006-01-13  9:56 performance problems James Harper
2006-01-13 10:04 ` Keir Fraser
2006-01-13  1:33 James Harper
2006-01-13  9:05 ` Keir Fraser
2006-01-13  1:18 James Harper
2006-01-13  0:39 Ian Pratt
2006-01-13  0:25 James Harper
2006-01-12 12:44 James Harper
2006-01-12 12:24 Ian Pratt
2006-01-12  6:29 James Harper
2005-02-04 13:08 Ian Pratt
2005-02-04 14:21 ` Henning Glawe
2005-02-04 17:15   ` Nivedita Singhvi
2005-01-19 21:02 Ian Pratt
2005-02-04  9:04 ` Henning Glawe
2005-01-19 20:35 Henning Glawe
2005-01-19 20:39 ` Ronald G. Minnich
2005-01-19 21:02 ` Andrew Theurer
2005-01-19 22:56 ` Luciano Miguel Ferreira Rocha

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=1366095730.3018.31.camel@localhost \
    --to=ceph.list-paemfetk6c1qfi55v6+gnq@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@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.