[MESOS-9509] Benchmark command health checks in default executor

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Done
• Component/s: executor
• Labels: default-executor foundations mesosphere perfomance
• Epic Link: TaskCheckingPerformance
• Sprint: Mesos Foundations R9 Sprint 37, Mesos Foundations: RI-13 Sp 44, Mesos Foundations: RI13 Sp 45, Mesos Foundations: RI14 Sp 46, Mesos Foundations: RI14 Sp 47
• Story Points: 5
• Assignee: Joseph Wu
• Reporter: Vinod Kone
• Shepherd: Greg Mann
• Created: 03/Jan/19 18:02
• Updated: 05/Jun/19 17:24
• Resolved: 05/Jun/19 17:23

Description

TCP/HTTP health checks were extensively scale tested as part of https://mesosphere.com/blog/introducing-mesos-native-health-checks-apache-mesos-part-2/.

We should do the same for command checks by default executor because it uses a very different mechanism (agent fork/execs the check command as a nested container) and will have very different scalability characteristics.

We should also use these benchmarks as an opportunity to produce perf traces of the Mesos agent (both with and without process inheritance) so that a thorough analysis of the performance can be done as part of MESOS-9513.