You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Zameer Manji (JIRA)" <ji...@apache.org> on 2016/09/08 00:33:20 UTC

[jira] [Commented] (AURORA-1766) Account for thermos executor overhead in reported CPU usage to user

    [ https://issues.apache.org/jira/browse/AURORA-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472258#comment-15472258 ] 

Zameer Manji commented on AURORA-1766:
--------------------------------------

I think [~StephanErb] is in favor of removing it. Maybe he can share his view on how to fix this. Maybe we should just have "minimum job size"?

> Account for thermos executor overhead in reported CPU usage to user
> -------------------------------------------------------------------
>
>                 Key: AURORA-1766
>                 URL: https://issues.apache.org/jira/browse/AURORA-1766
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Rick Mangi
>
> The default .25 CPU overhead taken for thermos can be hugely impactful on clusters with many tasks and it's not reported to the user in the web UI. Ideally the resources used by the cluster should be reported accurately. We ran into a case where we could not launch jobs even though we thought we had plenty of free cores. 
> Alternatively, the thermos overhead could be removed completely. I think it's confusing personally.



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