aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambert (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-1158) Consider finding preemption slots asynchronously
Date Tue, 31 Mar 2015 03:53:54 GMT

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

Chris Lambert updated AURORA-1158:
----------------------------------
    Sprint: Twitter Aurora Q1'15 Sprint 4, Twitter Aurora Q1'15 Sprint 5, Twitter Aurora Q1'15
Sprint 6  (was: Twitter Aurora Q1'15 Sprint 4, Twitter Aurora Q1'15 Sprint 5)

> Consider finding preemption slots asynchronously 
> -------------------------------------------------
>
>                 Key: AURORA-1158
>                 URL: https://issues.apache.org/jira/browse/AURORA-1158
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>
> The current Preemptor implementation performs synchronous preemption victim search. This
isn't necessary as resource swap cannot be performed within the same scheduling loop due to
victims taking time to vacate their premises (being killed). 
> Consider asynchronous victim search/killing instead. That will move the heavy lifting
out of the critical scheduling loop and remove "flat" preemptor perf tax applied on every
failed task scheduling/assignment.  



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

Mime
View raw message