[jira] [Assigned] (MESOS-9509) Benchmark command health checks in default executor

["Gastón Kleiman (JIRA)" <ji...@apache.org>]

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

Gastón Kleiman reassigned MESOS-9509:
-------------------------------------

    Assignee: Gastón Kleiman  (was: Greg Mann)

> Benchmark command health checks in default executor
> ---------------------------------------------------
>
>                 Key: MESOS-9509
>                 URL: https://issues.apache.org/jira/browse/MESOS-9509
>             Project: Mesos
>          Issue Type: Task
>          Components: executor
>            Reporter: Vinod Kone
>            Assignee: Gastón Kleiman
>            Priority: Major
>              Labels: default-executor, foundations, mesosphere, perfomance
>         Attachments: check-rate.png, check-responsiveness.png, mesos-mwstpublicagent1-soak113s.testing.mesosphe.re-22-37.stacks.gz, multi-healthcheck-large-pod-executor-logs.tar.gz, mwstpublicagent1-soak113s.testing.mesosphe.re.mesos-agent.log.gz
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)