You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Meng Zhu (JIRA)" <ji...@apache.org> on 2019/06/03 00:55:00 UTC
[jira] [Created] (MESOS-9806) Address allocator performance
regression due to the removal of quota role sorter.
Meng Zhu created MESOS-9806:
-------------------------------
Summary: Address allocator performance regression due to the removal of quota role sorter.
Key: MESOS-9806
URL: https://issues.apache.org/jira/browse/MESOS-9806
Project: Mesos
Issue Type: Improvement
Components: allocation
Reporter: Meng Zhu
Assignee: Meng Zhu
In MESOS-9802, we removed the quota role sorter which is tech debt.
However, this slows down the allocator. The problem is that in the first stage, even though a cluster might have no active roles with non-default quota, the allocator will now have to sort and go through each and every role in the cluster. Benchmark result shows that for 1k roles with 2k frameworks, the allocator could experience ~50% performance degradation.
There are a couple of ways to address this issue. For example, we could make the sorter aware of quota. And add a method, say `sortQuotaRoles`, to return all the roles with non-default quota. Alternatively, an even better approach would be to deprecate the sorter concept and just have two standalone functions e.g. sortRoles() and sortQuotaRoles() that takes in the role tree structure (not yet exist in the allocator) and return the sorted roles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)