[
https://issues.apache.org/jira/browse/MESOS-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779877#comment-16779877
]
Gastón Kleiman edited comment on MESOS-9509 at 2/27/19 11:36 PM:
-----------------------------------------------------------------
Attached some recent agent perf traces, agent logs and default executor logs
from a Mesos (sha 3886e2a0b77a8f8233d95f785ddb55403e638677) agent (EC2
r4.16xlarge) running a pod with 200 tasks with health checks.
was (Author: gkleiman):
Attached some recent agent perf traces, agent logs and default executor logs
from a Mesos (sha 3886e2a0b77a8f8233d95f785ddb55403e638677) agent running a pod
with 200 tasks with health checks.
> 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: Greg Mann
> 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)
