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

Posted to issues@mesos.apache.org by "Michael Park (JIRA)" <ji...@apache.org> on 2016/02/27 01:45:18 UTC

[jira] [Updated] (MESOS-3052) Allocator performance issue when using a large number of filters.

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

Michael Park updated MESOS-3052:
--------------------------------
    Fix Version/s: 0.24.2

> Allocator performance issue when using a large number of filters.
> -----------------------------------------------------------------
>
>                 Key: MESOS-3052
>                 URL: https://issues.apache.org/jira/browse/MESOS-3052
>             Project: Mesos
>          Issue Type: Bug
>          Components: allocation
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 0.25.0, 0.24.2
>
>         Attachments: MESOS-3052.tiff
>
>
> With a large number of frameworks that all refuse offers permanently, the filter lists can get long. Comparing the slave IDs on the long filter lists ends up taking noticeable time.
> Since each filter list traversal matches on on a single slave ID, we can optimize this by hashing the slave ID and checking the hash before comparing the full slave ID. This is a 5% - 10% performance win.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)