[
https://issues.apache.org/jira/browse/YUNIKORN-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403200#comment-17403200
]
Craig Condit commented on YUNIKORN-807:
---------------------------------------
[~sunilg], thanks for the feedback. I agree with using a followup Jira to
address specific scheduler behavior – this one is explicitly about refactoring
/ performance improvement.
I don't foresee hotspotting in nodeUpdated handling being a real problem.
Updates should be relatively infrequent per node, and the locks are taken
per-node.
> Improve performance of node sorting
> -----------------------------------
>
> Key: YUNIKORN-807
> URL: https://issues.apache.org/jira/browse/YUNIKORN-807
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
> Labels: pull-request-available
> Attachments: Node Sorting Performance Improvement.pdf
>
>
> YuniKorn currently sorts all nodes on demand whenever scheduling of a
> container occurs. This causes significant performance degradation as the
> number of nodes increases.
> If we replace the on-demand sorting with a B-Tree sorted proactively, we can
> improve performance considerably.
> This is a similar approach to YUNIKORN-21, but without the associated
> behavioral changes.
> I've attached a design document with the details of the approach and the
> performance improvement gained.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
