[MESOS-2834] Support different perf output formats

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: containerization
• Labels: twitter
• Sprint: Twitter Mesos Q2 Sprint 6, Twitter Mesos Q3 Sprint 1, Twitter Mesos Q3 Sprint 2, Twitter Mesos Q3 Sprint 3, Twitter Mesos Q3 Sprint 4
• Story Points: 3
• Assignee: Paul Brett
• Reporter: Ian Downes
• Shepherd: Benjamin Mahler
• Created: 09/Jun/15 04:32
• Updated: 26/Apr/17 16:54
• Resolved: 21/Sep/15 16:45

Description

The output format of perf changes in 3.14 (inserting an additional field) and in again in 4.1 (appending additional) fields. See kernel commits:
410136f5dd96b6013fe6d1011b523b1c247e1ccb
d73515c03c6a2706e088094ff6095a3abefd398b

Update the perf::parse() function to understand all these formats.

Issue Links

• is blocked by: MESOS-3185 Refactor Subprocess logic in linux/perf.cpp to use common subroutine
• is depended upon by: MESOS-3050 Failing ROOT_ tests on CentOS 7.1
• is related to: MESOS-4705 Linux 'perf' parsing logic may fail when OS distribution has perf backports.
• is related to: MESOS-3399 Rewrite perf events code