[MESOS-8851] Introduce a push-based gauge.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 1.6.0
• Component/s: libprocess
• Labels: mesosphere metrics
• Sprint: Mesosphere Sprint 78
• Story Points: 3
• Assignee: Benjamin Mahler
• Reporter: Benjamin Mahler
• Shepherd: Gilbert Song
• Created: 26/Apr/18 21:47
• Updated: 14/May/18 21:27
• Resolved: 27/Apr/18 23:25

Description

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.

Issue Links

• is related to: MESOS-8914 Migrate pull gauges to push gauges.