[ https://issues.apache.org/jira/browse/MESOS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764212#comment-13764212 ]
Sam Taha commented on MESOS-687: -------------------------------- Some of these stats can be useful to report back to user/framework to keep track of the cost of a particular job like how much cpu time and memory the job/task is consuming. > slave should export perf hardware counters when available > --------------------------------------------------------- > > Key: MESOS-687 > URL: https://issues.apache.org/jira/browse/MESOS-687 > Project: Mesos > Issue Type: Story > Components: slave > Reporter: brian wickman > Priority: Minor > > It would be very valuable for the slave resource monitor to export hardware > counters. There are a few ways this could be done -- either by invoking perf > directly or by accessing the counters via the syscall/read interface > described by http://lxr.free-electrons.com/source/tools/perf/design.txt I'd > imagine this would just get plumbed through Isolator::usage in the end and > get exported via the resource monitor endpoint. > Correct me if I'm wrong but there's currently no information exposed > (programmatically) at the granularity level of executor, so I don't really > know how this information could ever make its way into the hands of a > scheduler for the purpose of making better scheduling decisions vis-a-vis > things like task-level interference. Given Google's CPI paper > (http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/pubs/archive/40737.pdf) > it sounds like something worth investigating. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira