[
https://issues.apache.org/jira/browse/YUNIKORN-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032533#comment-18032533
]
Adrian Lin commented on YUNIKORN-2057:
--------------------------------------
Hi,
I noticed this issue has been stalled for a while.
I've submitted a pull request for this issue, and I hope it helps
https://github.com/apache/yunikorn-core/pull/1037
> FindQueueByAppID is slow
> ------------------------
>
> Key: YUNIKORN-2057
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2057
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler
> Reporter: Wilfred Spiegelenburg
> Assignee: Tarun Parimi
> Priority: Critical
> Labels: pull-request-available
>
> The preemptor calls {{p.queue.FindQueueByAppID()}} to figure out which queue
> the application runs in. This is an expensive way to retrieve the queue.
> Especially when the queue structure grows large and there is no fencing
> turned on with could be traversing large numbers of queue and doing even more
> lookups. We also do this for every single victim. That could be a list and we
> could be trying multiple nodes increasing the number of times we make that
> call.
> We should leverage the application tracking at the partition level to do a
> simple call:
> PartitionContext.getApplicationQueue(appID string) *Queue
> This will require some "plumbing" like we did with the node functions but it
> will perform much better.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
