[
https://issues.apache.org/jira/browse/MESOS-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971908#comment-15971908
]
Adam B edited comment on MESOS-6405 at 4/18/17 12:47 AM:
---------------------------------------------------------
Patch was discarded over a month ago due to inactivity, so I'm moving this back
to "Accepted" and removing the 1.2.1 target Version, since it doesn't seem
urgent enough for a backport, or actually in progress/review for 1.2.x.
Let's land it in master when we can and then consider backporting if necessary.
was (Author: adam-mesos):
Patch was discarded over a month ago due to inactivity, so I'm moving this back
to "Accepted" and removing the 1.2.1 fixVersion, since it doesn't seem urgent
enough for a backport, or actually in progress/review for 1.2.x.
Let's land it in master when we can and then consider backporting if necessary.
> Benchmark call ingestion path on the Mesos master.
> --------------------------------------------------
>
> Key: MESOS-6405
> URL: https://issues.apache.org/jira/browse/MESOS-6405
> Project: Mesos
> Issue Type: Improvement
> Components: master, scheduler api
> Reporter: Anand Mazumdar
> Assignee: Anand Mazumdar
> Priority: Critical
> Labels: mesosphere
>
> [~drexin] reported on the user mailing
> [list|http://mail-archives.apache.org/mod_mbox/mesos-user/201610.mbox/%3C6B42E374-9AB7-4444-A315-A6558753E08B%40apple.com%3E]
> that there seems to be a significant regression in performance on the call
> ingestion path on the Mesos master wrt to the scheduler driver (v0 API).
> We should create a benchmark to first get a sense of the numbers and then go
> about fixing the performance issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
