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

["Anand Mazumdar (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924548#comment-15924548 ] 

Anand Mazumdar commented on MESOS-6405:
---------------------------------------

Reasons for slowness observed based on running the benchmark:

On the master:
- The root cause for most of the slowness observed in the benchmark when comparing v0/v1 is due to the extra copies of the {{Request}} object being created from the time the decoder parses the object to the time the actual HTTP handler is invoked. We are creating ~5 copies of the {{Request}} object. 

On the client:
- The other major cause of slowness observed in the benchmark is due to the client (scheduler library). Most of the slowness there is due to the {{Call}} object being copied multiple times and also due to creating a couple of {{Request}} object copies in the {{Connection}} abstraction.


> 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)