[jira] [Commented] (MESOS-1458) Restore "cpus" metric in addition to cpu_*_secs counters in container stats

["Benjamin Mahler (JIRA)" <ji...@apache.org>]

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

Benjamin Mahler commented on MESOS-1458:
----------------------------------------

Could you provide some use-case examples?

Specifically I'm looking to understand the whether it would be sufficient to instead build 'top'-like tooling on top of the existing endpoint. What I mean by this is to have client-side polling of the endpoint to compute cpu usage, this lets the client determine the polling interval. This is analogous to how {{top}} provides cpu usage by leveraging the total cpu time information.

The reason we removed this metric is because for a "cpus_used" metric to be useful, we must expose the polling interval as well. At this point, it's hard to make everyone happy because different clients may want different polling intervals.

> Restore "cpus" metric in addition to cpu_*_secs counters in container stats
> ---------------------------------------------------------------------------
>
>                 Key: MESOS-1458
>                 URL: https://issues.apache.org/jira/browse/MESOS-1458
>             Project: Mesos
>          Issue Type: Story
>          Components: isolation, slave
>    Affects Versions: 0.18.0
>            Reporter: Kevin Sweeney
>
> While a "cpu-seconds per second" metric can be computed with 2 samples of cpu_*_secs at different times, it's often convenient to have a single self-contained value, for example if sample collection interval is long, or so that an operator can glance at the cpu usage of a task with a single curl command.
> Add user_cpus, system_cpus, and total_cpus metrics to the available container stats.



--
This message was sent by Atlassian JIRA
(v6.2#6252)