Metrics for association

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Metrics for association

jewzaam
Administrator
Wondering how we might capture metrics specific to association.  How much overhead does it add?  The simplest thing I can think of is put functionality into a Hystrix command so it just gets published with other metrics.

Thoughts?
Reply | Threaded
Open this post in threaded view
|

Re: Metrics for association

lcestari
Seems pretty nice idea, not sure if we can do it easily with Hystrix, but maybe it is possible (hacking Hystrix I guess). It would be a nice idea for a hackfest (if someone do some research before hand) 

Luan Cestari | Senior Software Applications Engineer
IT Shared Services
M: +55 11 99602-7887
<img src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg" alt="Red Hat" border="0" data-mce-src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg" data-mce-style="font-family: Arial; font-size: 13px;" style="font-family: Arial; font-size: 13px;">
Better technology. Faster innovation. Powered by community collaboration. 
See how it works at www.redhat.com
 




From: "jewzaam [via lightblue-dev]" <[hidden email]>
To: "lcestari" <[hidden email]>
Sent: Monday, January 12, 2015 1:50:11 PM
Subject: Metrics for association

Wondering how we might capture metrics specific to association.  How much overhead does it add?  The simplest thing I can think of is put functionality into a Hystrix command so it just gets published with other metrics.

Thoughts?


If you reply to this email, your message will be added to the discussion below:
http://dev.forum.lightblue.io/Metrics-for-association-tp278.html
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

Re: Metrics for association

jewzaam
Administrator
For hystrix it would just be putting all the logic for doing association into one or more hystrix command implementations.  Each command will publish metrics.

On Mon Jan 12 2015 at 12:02:08 PM lcestari [via lightblue-dev] <[hidden email]> wrote:
Seems pretty nice idea, not sure if we can do it easily with Hystrix, but maybe it is possible (hacking Hystrix I guess). It would be a nice idea for a hackfest (if someone do some research before hand) 

Luan Cestari | Senior Software Applications Engineer
IT Shared Services
M: +55 11 99602-7887
<img src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg" alt="Red Hat" border="0" data-mce-src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg" data-mce-style="font-family: Arial; font-size: 13px;" style="font-family: Arial; font-size: 13px;">
Better technology. Faster innovation. Powered by community collaboration. 
See how it works at www.redhat.com
 




From: "jewzaam [via lightblue-dev]" <[hidden email]>
To: "lcestari" <[hidden email]>
Sent: Monday, January 12, 2015 1:50:11 PM
Subject: Metrics for association


Wondering how we might capture metrics specific to association.  How much overhead does it add?  The simplest thing I can think of is put functionality into a Hystrix command so it just gets published with other metrics.

Thoughts?


If you reply to this email, your message will be added to the discussion below:
http://dev.forum.lightblue.io/Metrics-for-association-tp278.html
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML
If you reply to this email, your message will be added to the discussion below:
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: Metrics for association

bserdar
The mediator decides whether or not to use associations based on the
number of entities in the retrieval entity. So, that logic in mediator
can be extracted out to a hystrix command. But, what's the value of
this? The metrics we'll get will be the metrics for retrieving
composite entities.

On Mon, Jan 12, 2015 at 10:13 AM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> For hystrix it would just be putting all the logic for doing association
> into one or more hystrix command implementations.  Each command will publish
> metrics.
>
> On Mon Jan 12 2015 at 12:02:08 PM lcestari [via lightblue-dev] <[hidden
> email]> wrote:
>>
>> Seems pretty nice idea, not sure if we can do it easily with Hystrix, but
>> maybe it is possible (hacking Hystrix I guess). It would be a nice idea for
>> a hackfest (if someone do some research before hand)
>>
>> Luan Cestari | Senior Software Applications Engineer
>> IT Shared Services
>> M: +55 11 99602-7887
>> <img
>> src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg"
>> alt="Red Hat" border="0"
>> data-mce-src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg"
>> data-mce-style="font-family: Arial; font-size: 13px;" style="font-family:
>> Arial; font-size: 13px;">
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at www.redhat.com
>>
>>
>>
>>
>> ________________________________
>> From: "jewzaam [via lightblue-dev]" <[hidden email]>
>> To: "lcestari" <[hidden email]>
>> Sent: Monday, January 12, 2015 1:50:11 PM
>> Subject: Metrics for association
>>
>>
>> Wondering how we might capture metrics specific to association.  How much
>> overhead does it add?  The simplest thing I can think of is put
>> functionality into a Hystrix command so it just gets published with other
>> metrics.
>>
>> Thoughts?
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/Metrics-for-association-tp278.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/Metrics-for-association-tp278p279.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://dev.forum.lightblue.io/Metrics-for-association-tp278p280.html
> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML
Reply | Threaded
Open this post in threaded view
|

Re: Metrics for association

jewzaam
Administrator
What I would like to see is how much overhead association adds on top of retrieval of individual entities.  Maybe hystrix isn't the right answer for that given the comparison wouldn't really be clear.  You could look at:
* REST commands: time to process requests
* association commands: time to process associations
* backend commands: time to process backend requests

In the case of the REST commands it will include the association and backend times.
For association commands it would also include backend times.

There's no clear way to answer how much overhead there is.  But we could see how many requests used associations vs not and figure something based on the data.  It would be just loose interpretations though.

Another option is capturing somewhere else detailed metrics about each request.  Sort of a request audit trail.

On Mon Jan 12 2015 at 12:25:02 PM bserdar [via lightblue-dev] <[hidden email]> wrote:
The mediator decides whether or not to use associations based on the
number of entities in the retrieval entity. So, that logic in mediator
can be extracted out to a hystrix command. But, what's the value of
this? The metrics we'll get will be the metrics for retrieving
composite entities.

On Mon, Jan 12, 2015 at 10:13 AM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> For hystrix it would just be putting all the logic for doing association
> into one or more hystrix command implementations.  Each command will publish
> metrics.
>
> On Mon Jan 12 2015 at 12:02:08 PM lcestari [via lightblue-dev] <[hidden
> email]> wrote:

>>
>> Seems pretty nice idea, not sure if we can do it easily with Hystrix, but
>> maybe it is possible (hacking Hystrix I guess). It would be a nice idea for
>> a hackfest (if someone do some research before hand)
>>
>> Luan Cestari | Senior Software Applications Engineer
>> IT Shared Services
>> M: +55 11 99602-7887
>> <img
>> src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg"
>> alt="Red Hat" border="0"
>> data-mce-src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg"
>> data-mce-style="font-family: Arial; font-size: 13px;" style="font-family:
>> Arial; font-size: 13px;">
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at www.redhat.com
>>
>>
>>
>>
>> ________________________________
>> From: "jewzaam [via lightblue-dev]" <[hidden email]>
>> To: "lcestari" <[hidden email]>
>> Sent: Monday, January 12, 2015 1:50:11 PM
>> Subject: Metrics for association
>>
>>
>> Wondering how we might capture metrics specific to association.  How much
>> overhead does it add?  The simplest thing I can think of is put
>> functionality into a Hystrix command so it just gets published with other
>> metrics.
>>
>> Thoughts?
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/Metrics-for-association-tp278.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/Metrics-for-association-tp278p279.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:

> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML
If you reply to this email, your message will be added to the discussion below:
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: Metrics for association

bserdar
How will we compare that? If you retrieve a simple entity, no
association related code is run. If you retrieve a composite entity,
then there will be multiple simple entity retrievals, and the
retrievals will dominate the execution time.

On Mon, Jan 12, 2015 at 10:36 AM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> What I would like to see is how much overhead association adds on top of
> retrieval of individual entities.  Maybe hystrix isn't the right answer for
> that given the comparison wouldn't really be clear.  You could look at:
> * REST commands: time to process requests
> * association commands: time to process associations
> * backend commands: time to process backend requests
>
> In the case of the REST commands it will include the association and backend
> times.
> For association commands it would also include backend times.
>
> There's no clear way to answer how much overhead there is.  But we could see
> how many requests used associations vs not and figure something based on the
> data.  It would be just loose interpretations though.
>
> Another option is capturing somewhere else detailed metrics about each
> request.  Sort of a request audit trail.
>
> On Mon Jan 12 2015 at 12:25:02 PM bserdar [via lightblue-dev] <[hidden
> email]> wrote:
>>
>> The mediator decides whether or not to use associations based on the
>> number of entities in the retrieval entity. So, that logic in mediator
>> can be extracted out to a hystrix command. But, what's the value of
>> this? The metrics we'll get will be the metrics for retrieving
>> composite entities.
>>
>> On Mon, Jan 12, 2015 at 10:13 AM, jewzaam [via lightblue-dev]
>> <[hidden email]> wrote:
>>
>> > For hystrix it would just be putting all the logic for doing association
>> > into one or more hystrix command implementations.  Each command will
>> > publish
>> > metrics.
>> >
>> > On Mon Jan 12 2015 at 12:02:08 PM lcestari [via lightblue-dev] <[hidden
>> > email]> wrote:
>>
>> >>
>> >> Seems pretty nice idea, not sure if we can do it easily with Hystrix,
>> >> but
>> >> maybe it is possible (hacking Hystrix I guess). It would be a nice idea
>> >> for
>> >> a hackfest (if someone do some research before hand)
>> >>
>> >> Luan Cestari | Senior Software Applications Engineer
>> >> IT Shared Services
>> >> M: +55 11 99602-7887
>> >> <img
>> >>
>> >> src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg"
>> >> alt="Red Hat" border="0"
>> >>
>> >> data-mce-src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg"
>> >> data-mce-style="font-family: Arial; font-size: 13px;"
>> >> style="font-family:
>> >> Arial; font-size: 13px;">
>> >> Better technology. Faster innovation. Powered by community
>> >> collaboration.
>> >> See how it works at www.redhat.com
>> >>
>> >>
>> >>
>> >>
>> >> ________________________________
>> >> From: "jewzaam [via lightblue-dev]" <[hidden email]>
>> >> To: "lcestari" <[hidden email]>
>> >> Sent: Monday, January 12, 2015 1:50:11 PM
>> >> Subject: Metrics for association
>> >>
>> >>
>> >> Wondering how we might capture metrics specific to association.  How
>> >> much
>> >> overhead does it add?  The simplest thing I can think of is put
>> >> functionality into a Hystrix command so it just gets published with
>> >> other
>> >> metrics.
>> >>
>> >> Thoughts?
>> >>
>> >> ________________________________
>> >> If you reply to this email, your message will be added to the
>> >> discussion
>> >> below:
>> >> http://dev.forum.lightblue.io/Metrics-for-association-tp278.html
>> >> To start a new topic under lightblue-dev, email [hidden email]
>> >> To unsubscribe from lightblue-dev, click here.
>> >> NAML
>> >> If you reply to this email, your message will be added to the
>> >> discussion
>> >> below:
>> >> http://dev.forum.lightblue.io/Metrics-for-association-tp278p279.html
>> >> To start a new topic under lightblue-dev, email [hidden email]
>> >> To unsubscribe from lightblue-dev, click here.
>> >> NAML
>> >
>> >
>> >
>> > ________________________________
>> > If you reply to this email, your message will be added to the discussion
>> > below:
>> > http://dev.forum.lightblue.io/Metrics-for-association-tp278p280.html
>>
>> > To start a new topic under lightblue-dev, email
>> > [hidden email]
>> > To unsubscribe from lightblue-dev, click here.
>> > NAML
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/Metrics-for-association-tp278p281.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
> http://dev.forum.lightblue.io/Metrics-for-association-tp278p282.html
> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML
Reply | Threaded
Open this post in threaded view
|

Re: Metrics for association

jewzaam
Administrator
From hystrix data, we can't compare.  If we want to get specific info on request performance at a level deeper than the REST layer and be able to keep a specific request's metrics bundled together we have to do something different.  So, hystrix is out.  We could track start time and end time for various steps along a request's path and at the end store the numbers in a database or log file.

On Mon Jan 12 2015 at 12:56:30 PM bserdar [via lightblue-dev] <[hidden email]> wrote:
How will we compare that? If you retrieve a simple entity, no
association related code is run. If you retrieve a composite entity,
then there will be multiple simple entity retrievals, and the
retrievals will dominate the execution time.

On Mon, Jan 12, 2015 at 10:36 AM, jewzaam [via lightblue-dev]
<[hidden email]> wrote:

> What I would like to see is how much overhead association adds on top of
> retrieval of individual entities.  Maybe hystrix isn't the right answer for
> that given the comparison wouldn't really be clear.  You could look at:
> * REST commands: time to process requests
> * association commands: time to process associations
> * backend commands: time to process backend requests
>
> In the case of the REST commands it will include the association and backend
> times.
> For association commands it would also include backend times.
>
> There's no clear way to answer how much overhead there is.  But we could see
> how many requests used associations vs not and figure something based on the
> data.  It would be just loose interpretations though.
>
> Another option is capturing somewhere else detailed metrics about each
> request.  Sort of a request audit trail.
>
> On Mon Jan 12 2015 at 12:25:02 PM bserdar [via lightblue-dev] <[hidden
> email]> wrote:

>>
>> The mediator decides whether or not to use associations based on the
>> number of entities in the retrieval entity. So, that logic in mediator
>> can be extracted out to a hystrix command. But, what's the value of
>> this? The metrics we'll get will be the metrics for retrieving
>> composite entities.
>>
>> On Mon, Jan 12, 2015 at 10:13 AM, jewzaam [via lightblue-dev]
>> <[hidden email]> wrote:
>>
>> > For hystrix it would just be putting all the logic for doing association
>> > into one or more hystrix command implementations.  Each command will
>> > publish
>> > metrics.
>> >
>> > On Mon Jan 12 2015 at 12:02:08 PM lcestari [via lightblue-dev] <[hidden
>> > email]> wrote:
>>
>> >>
>> >> Seems pretty nice idea, not sure if we can do it easily with Hystrix,
>> >> but
>> >> maybe it is possible (hacking Hystrix I guess). It would be a nice idea
>> >> for
>> >> a hackfest (if someone do some research before hand)
>> >>
>> >> Luan Cestari | Senior Software Applications Engineer
>> >> IT Shared Services
>> >> M: +55 11 99602-7887
>> >> <img
>> >>
>> >> src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg"
>> >> alt="Red Hat" border="0"
>> >>
>> >> data-mce-src="http://images.engage.redhat.com/eloquaimages/clients/RedHat/{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg"
>> >> data-mce-style="font-family: Arial; font-size: 13px;"
>> >> style="font-family:
>> >> Arial; font-size: 13px;">
>> >> Better technology. Faster innovation. Powered by community
>> >> collaboration.
>> >> See how it works at www.redhat.com
>> >>
>> >>
>> >>
>> >>
>> >> ________________________________
>> >> From: "jewzaam [via lightblue-dev]" <[hidden email]>
>> >> To: "lcestari" <[hidden email]>
>> >> Sent: Monday, January 12, 2015 1:50:11 PM
>> >> Subject: Metrics for association
>> >>
>> >>
>> >> Wondering how we might capture metrics specific to association.  How
>> >> much
>> >> overhead does it add?  The simplest thing I can think of is put
>> >> functionality into a Hystrix command so it just gets published with
>> >> other
>> >> metrics.
>> >>
>> >> Thoughts?
>> >>
>> >> ________________________________
>> >> If you reply to this email, your message will be added to the
>> >> discussion
>> >> below:
>> >> http://dev.forum.lightblue.io/Metrics-for-association-tp278.html
>> >> To start a new topic under lightblue-dev, email [hidden email]
>> >> To unsubscribe from lightblue-dev, click here.
>> >> NAML
>> >> If you reply to this email, your message will be added to the
>> >> discussion
>> >> below:
>> >> http://dev.forum.lightblue.io/Metrics-for-association-tp278p279.html
>> >> To start a new topic under lightblue-dev, email [hidden email]
>> >> To unsubscribe from lightblue-dev, click here.
>> >> NAML
>> >
>> >
>> >
>> > ________________________________
>> > If you reply to this email, your message will be added to the discussion
>> > below:
>> > http://dev.forum.lightblue.io/Metrics-for-association-tp278p280.html
>>
>> > To start a new topic under lightblue-dev, email
>> > [hidden email]
>> > To unsubscribe from lightblue-dev, click here.
>> > NAML
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://dev.forum.lightblue.io/Metrics-for-association-tp278p281.html
>> To start a new topic under lightblue-dev, email [hidden email]
>> To unsubscribe from lightblue-dev, click here.
>> NAML
>
>
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:

> To start a new topic under lightblue-dev, email
> [hidden email]
> To unsubscribe from lightblue-dev, click here.
> NAML
If you reply to this email, your message will be added to the discussion below:
To start a new topic under lightblue-dev, email [hidden email]
To unsubscribe from lightblue-dev, click here.
NAML