All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Danilov <kdanilov@mirantis.com>
To: dillaman@redhat.com
Cc: John Spray <jspray@redhat.com>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Get IO request execution profile
Date: Mon, 23 Jan 2017 17:59:54 +0200	[thread overview]
Message-ID: <CACxKWaz6FxPO2VcFJy1+coOewFCwF2=0+feR5sDb3DrnGgvW4A@mail.gmail.com> (raw)
In-Reply-To: <CA+aFP1Av7jHmT4sFD4ysCeeFk_GwZSsAS2W8Zs-9nmcB3sCd4Q@mail.gmail.com>

> Potentially interesting idea, although it's not obvious to me why it's
useful to have this dumped on the client rather than the server?

The idea is to monitor requests execution time per stage.
dump_historic_ops covers large part of this idea, meanwhile in case of
large cluster
it hard follow particular request. You have to calculate primary OSD
for it. Historic
store only slowest requests. To get a timing profile historic ops buffer have to
increased to fit all requests.

So if you like to get a requests execution profile(and potentially
monitor how it changes over time)
you can very easily get it for slowest requests, but for all kind of
requests it requires tricks and
put unnecessary additional load on OSD nodes.

> Have you looked at the Zipkin tracking PR [1]?
Nope. Is there any plans to merge it?

Thanks

On Mon, Jan 23, 2017 at 3:59 PM, Jason Dillaman <jdillama@redhat.com> wrote:
> Have you looked at the Zipkin tracking PR [1]?
>
> [1] https://github.com/ceph/ceph/pull/11053
>
> On Mon, Jan 23, 2017 at 7:54 AM, John Spray <jspray@redhat.com> wrote:
>> On Mon, Jan 23, 2017 at 12:36 PM, Konstantin Danilov
>> <kdanilov@mirantis.com> wrote:
>>> Hi all,
>>>
>>> is there a way to get something like 'dump historic ops' for particular request?
>>> Probably from client side. Ideally I'd like to send a normal IO
>>> request with special
>>> flag and get execution profile in response metadata.
>>> If it's not possible right now - is this an interesting feature to
>>> implement, or I miss
>>> something and it's useless?
>>
>> Potentially interesting idea, although it's not obvious to me why it's
>> useful to have this dumped on the client rather than the server?
>> Would be it equally useful to be able to tag a specific client on the
>> server side to have its requests dumped like this?
>>
>> John
>>
>>>
>>> Thanks
>>>
>>> --
>>> Kostiantyn Danilov aka koder.ua
>>> Principal software engineer, Mirantis
>>>
>>> skype:koder.ua
>>> http://koder-ua.blogspot.com/
>>> http://mirantis.com
>>> --
>>> 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
>> --
>> 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
>
>
>
> --
> Jason



-- 
Kostiantyn Danilov aka koder.ua
Principal software engineer, Mirantis

skype:koder.ua
http://koder-ua.blogspot.com/
http://mirantis.com

  reply	other threads:[~2017-01-23 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 12:36 Get IO request execution profile Konstantin Danilov
2017-01-23 12:54 ` John Spray
2017-01-23 13:59   ` Jason Dillaman
2017-01-23 15:59     ` Konstantin Danilov [this message]
2017-01-23 16:02       ` Jason Dillaman
2017-01-24  0:12   ` Gregory Farnum

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='CACxKWaz6FxPO2VcFJy1+coOewFCwF2=0+feR5sDb3DrnGgvW4A@mail.gmail.com' \
    --to=kdanilov@mirantis.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dillaman@redhat.com \
    --cc=jspray@redhat.com \
    /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.