[jira] [Updated] (MESOS-8098) Benchmark Master failover performance

["Yan Xu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yan Xu updated MESOS-8098:
--------------------------
    Attachment: withoutperfpatches.perf.svg
                withperfpatches.perf.svg

Attaching two flame graphs comparing the benchmark running against the two versions below:

withperfpatches.perf.svg: https://github.com/apache/mesos/commit/41193181d6b75eeecae2729bf98007d9318e351a (close to the HEAD when the benchmark was created).

vs. 

withoutperfpatches.perf.svg: https://github.com/apache/mesos/commit/d9c90bf1d9c8b3a7dcc47be0cb773efff57cfb9d (before https://issues.apache.org/jira/browse/MESOS-7713 was merged)

The perf data was captured with me invoking gdb-mesos-tests.sh -> setting two break points on the two {{cout}} lines (right before and after the bulk reregistration) -> run -> coordinate {{perf record}} with the break points so it only captures the process behavior in between.

However I couldn't find much useful info from the resulting graphs. Perhaps someone can help me take a look? /cc [~bmahler] [~ipronin] [~dzhuk]?

> Benchmark Master failover performance
> -------------------------------------
>
>                 Key: MESOS-8098
>                 URL: https://issues.apache.org/jira/browse/MESOS-8098
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Yan Xu
>            Assignee: Yan Xu
>            Priority: Major
>         Attachments: withoutperfpatches.perf.svg, withperfpatches.perf.svg
>
>
> Master failover performance often sheds light on the master's performance in general as it's often the time the master experiences the highest load. Ways we can benchmark the failover include the time it takes for all agents to reregister, all frameworks to resubscribe or fully reconcile.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)