All of lore.kernel.org
 help / color / mirror / Atom feed
From: "hzwulibin" <hzwulibin@gmail.com>
To: Sage Weil <sage@newdream.net>, Gregory Farnum <gfarnum@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
	ceph-users <ceph-users@ceph.com>
Subject: Re:  Re: values of "ceph daemon osd.x perf dump objecters " are zero
Date: Thu, 29 Oct 2015 08:20:49 +0800	[thread overview]
Message-ID: <5631665A.1090304@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1510281707090.1004@cobra.newdream.net>

Sure, thanks!

But i think client like qemu use librbd will also run into this perf statistics, any way
we could dump the perf statistics for other client side like qemu.

Sorry if there exist some document on internet and i didn't got it by searching.

Thanks!

------------------				 
hzwulibin
2015-10-29

-------------------------------------------------------------
发件人:Sage Weil <sage@newdream.net>
发送日期:2015-10-29 08:07
收件人:Libin Wu
抄送:ceph-devel,ceph-users
主题:Re: values of "ceph daemon osd.x perf dump objecters " are zero

Objecter is the client side, but you're dumping stats on the osd.  The 
only time it is used as a client there is with cache tiering.

sage

On Wed, 28 Oct 2015, Libin Wu wrote:

> Hi, all
> 
> As my understand, command "ceph daemon osd.x perf dump objecters" should
> output the perf data of osdc(librados). But when i use this command,
> why all those values are zero expcept map_epoch and map_inc. Follow is
> the result(It has fio test with rbd ioengine on the cluster):
> 
> 
> $ sudo ceph daemon osd.10 perf dump objecter
> 
> {
> 
>     "objecter": {
> 
>         "op_active": 0,
> 
>         "op_laggy": 0,
> 
>         "op_send": 0,
> 
>         "op_send_bytes": 0,
> 
>         "op_resend": 0,
> 
>         "op_ack": 0,
> 
>         "op_commit": 0,
> 
>         "op": 0,
> 
>         "op_r": 0,
> 
>         "op_w": 0,
> 
>         "op_rmw": 0,
> 
>         "op_pg": 0,
> 
>         "osdop_stat": 0,
> 
>         "osdop_create": 0,
> 
>         "osdop_read": 0,
> 
>         "osdop_write": 0,
> 
>         "osdop_writefull": 0,
> 
>         "osdop_append": 0,
> 
>         "osdop_zero": 0,
> 
>         "osdop_truncate": 0,
> 
>         "osdop_delete": 0,
> 
>         "osdop_mapext": 0,
> 
>         "osdop_sparse_read": 0,
> 
>         "osdop_clonerange": 0,
> 
>         "osdop_getxattr": 0,
> 
>         "osdop_setxattr": 0,
> 
>         "osdop_cmpxattr": 0,
> 
>         "osdop_rmxattr": 0,
> 
>         "osdop_resetxattrs": 0,
> 
>         "osdop_tmap_up": 0,
> 
>         "osdop_tmap_put": 0,
> 
>         "osdop_tmap_get": 0,
> 
>         "osdop_call": 0,
> 
>         "osdop_watch": 0,
> 
>         "osdop_notify": 0,
> 
>         "osdop_src_cmpxattr": 0,
> 
>         "osdop_pgls": 0,
> 
>         "osdop_pgls_filter": 0,
> 
>         "osdop_other": 0,
> 
>         "linger_active": 0,
> 
>         "linger_send": 0,
> 
>         "linger_resend": 0,
> 
>         "linger_ping": 0,
> 
>         "poolop_active": 0,
> 
>         "poolop_send": 0,
> 
>         "poolop_resend": 0,
> 
>         "poolstat_active": 0,
> 
>         "poolstat_send": 0,
> 
>         "poolstat_resend": 0,
> 
>         "statfs_active": 0,
> 
>         "statfs_send": 0,
> 
>         "statfs_resend": 0,
> 
>         "command_active": 0,
> 
>         "command_send": 0,
> 
>         "command_resend": 0,
> 
>         "map_epoch": 2180,
> 
>         "map_full": 0,
> 
>         "map_inc": 83,
> 
>         "osd_sessions": 0,
> 
>         "osd_session_open": 0,
> 
>         "osd_session_close": 0,
> 
>         "osd_laggy": 0
> 
>     }
> 
> }
> 
> Anyone could tell why?
> 
> Thanks!
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 


      reply	other threads:[~2015-10-29  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 15:41 values of "ceph daemon osd.x perf dump objecters " are zero Libin Wu
2015-10-29  0:07 ` Sage Weil
2015-10-29  0:20   ` hzwulibin [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=5631665A.1090304@gmail.com \
    --to=hzwulibin@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@ceph.com \
    --cc=gfarnum@redhat.com \
    --cc=sage@newdream.net \
    /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.