[ 
https://issues.apache.org/jira/browse/MESOS-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460192#comment-16460192
 ] 

Benjamin Mahler commented on MESOS-8851:
----------------------------------------

What I wanted to convey was that, rather than the value getting "pushed into" 
the gauge by the gauge "server", the value gets "pulled out" of the "server".

Polling seems to often carry an implication of periodicity, like asking 
periodically for the value. I didn't want someone to think that there was some 
kind of built in polling specially related to this gauge variant.

That being said, I think both words get used interchangeably and would work 
here.

> Introduce a push-based gauge.
> -----------------------------
>
>                 Key: MESOS-8851
>                 URL: https://issues.apache.org/jira/browse/MESOS-8851
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess
>            Reporter: Benjamin Mahler
>            Assignee: Benjamin Mahler
>            Priority: Major
>              Labels: mesosphere, metrics
>             Fix For: 1.6.0
>
>
> Currently, we only have pull-based gauges which have significant performance 
> downsides.
> A push-based gauge differs from a pull-based gauge in that the client is 
> responsible for pushing the latest value into the gauge whenever it changes. 
> This can be challenging in some cases as it requires the client to have a 
> good handle on when the gauge value changes (rather than just computing the 
> current value when asked).
> It is highly recommended to use push-based gauges if possible as they provide 
> significant performance benefits over pull-based gauges. Pull-based gauge 
> suffer from delays getting processed on the event queue of a Process, as well 
> as incur computation cost on the Process each time the metrics are collected. 
> Push-based gauges, on the other hand, incur no cost to the owning Process 
> when metrics are collected, and instead incur a trivial cost when the Process 
> pushes new values in.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to