You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/11/10 16:15:58 UTC

[jira] [Updated] (MESOS-6405) Benchmark call ingestion path on the Mesos master.

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

Anand Mazumdar updated MESOS-6405:
----------------------------------
    Sprint: Mesosphere Sprint 45  (was: Mesosphere Sprint 45, Mesosphere Sprint 46)

> 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
>            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.4#6332)