[
https://issues.apache.org/jira/browse/MESOS-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241338#comment-16241338
]
Benjamin Mahler commented on MESOS-8098:
----------------------------------------
Looking through the bottom layer, I see the majority of the width is taken up
by protobuf serialization, de-serialization, copying and destruction. So that
should be a good area to focus on. Also, the profiling tools on macOS are
actually really nice I've found if you are ok with slowing down the program
significantly to get a more complete profile.
> 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
> 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)
