[
https://issues.apache.org/jira/browse/MESOS-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460236#comment-16460236
]
Benjamin Mahler commented on MESOS-8851:
----------------------------------------
[~zhitao] I think ultimately we will forbid pull-gauges in the master /
allocator / registrar and any other actors that do any non-trivial work. Help
converting the existing ones would be appreciated!
I think [~gilbert] is working on a master metrics benchmark that could help
measure the latency decrease for master metrics as we convert to push-gauges.
The other aspect of performance is how much master actor time we're spending
computing values, which is a subset of the overall response latency. This value
would become 0 when serving metrics requests if there are no pull-gauges.
> 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)