You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@submarine.apache.org by "cdmikechen (Jira)" <ji...@apache.org> on 2022/11/05 08:51:00 UTC
[jira] [Updated] (SUBMARINE-1175) The resource should be configured as [requests and limits] instead of single [limits]
[ https://issues.apache.org/jira/browse/SUBMARINE-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
cdmikechen updated SUBMARINE-1175:
----------------------------------
Target Version: 0.8.0
> The resource should be configured as [requests and limits] instead of single [limits]
> -------------------------------------------------------------------------------------
>
> Key: SUBMARINE-1175
> URL: https://issues.apache.org/jira/browse/SUBMARINE-1175
> Project: Apache Submarine
> Issue Type: Improvement
> Reporter: cdmikechen
> Priority: Major
>
> Submarine currently use *limit* to control resources in CRD.
> {code}
> resources:
> limits:
> cpu: '1'
> memory: 512M
> {code}
> Hope to suggest changing the [ *limits* ] to [ *requests* to *limits* ]. e.g.
> {code}
> resources:
> limits:
> cpu: '1'
> memory: 512M
> request:
> cpu: 0.5
> memory: 100M
> {code}
> This is a more rigorous resource description. Otherwise, the operator will lock all resource limits and requests in [cpu: '1'] and [memory: 512M] in pod.
> When adding a notebook, if the resources limits are large but the actual execution python process resources are small, the resource utilization is not high.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@submarine.apache.org
For additional commands, e-mail: dev-help@submarine.apache.org