[jira] [Updated] (SPARK-44758) Support memory limit configurable
[ https://issues.apache.org/jira/browse/SPARK-44758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SPARK-44758: --- Labels: pull-request-available (was: ) > Support memory limit configurable > - > > Key: SPARK-44758 > URL: https://issues.apache.org/jira/browse/SPARK-44758 > Project: Spark > Issue Type: Improvement > Components: Kubernetes >Affects Versions: 3.4.1 >Reporter: Mingliang Zhu >Priority: Minor > Labels: pull-request-available > > Currently the memory request and limit are set by summing the values of > spark.\{driver,executor}.memory and spark.\{driver,executor}.memoryOverhead. > Supporting memory limits configurable can bring some benefits. For example, > use unfixed memory to use page cache, reduce disk IO of shuffle read to > improve performance. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-44758) Support memory limit configurable
[ https://issues.apache.org/jira/browse/SPARK-44758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuml updated SPARK-44758: -- Description: Currently the memory request and limit are set by summing the values of spark.\{driver,executor}.memory and spark.\{driver,executor}.memoryOverhead. Supporting memory limits configurable can bring some benefits. For example, use unfixed memory to use page cache, reduce disk IO of shuffle read to improve performance. (was: Currently the memory request and limit are set by summing the values of spark.\{driver,executor}.memory and spark.\{driver,executor}.memoryOverhead. Supporting configurable memory limits can bring some benefits. For example, use unfixed memory to use page cache, reduce disk IO of shuffle read to improve performance.) > Support memory limit configurable > - > > Key: SPARK-44758 > URL: https://issues.apache.org/jira/browse/SPARK-44758 > Project: Spark > Issue Type: Improvement > Components: Kubernetes >Affects Versions: 3.4.1 >Reporter: zhuml >Priority: Minor > > Currently the memory request and limit are set by summing the values of > spark.\{driver,executor}.memory and spark.\{driver,executor}.memoryOverhead. > Supporting memory limits configurable can bring some benefits. For example, > use unfixed memory to use page cache, reduce disk IO of shuffle read to > improve performance. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-44758) Support memory limit configurable
[ https://issues.apache.org/jira/browse/SPARK-44758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhuml updated SPARK-44758: -- Summary: Support memory limit configurable (was: Support memory limit) > Support memory limit configurable > - > > Key: SPARK-44758 > URL: https://issues.apache.org/jira/browse/SPARK-44758 > Project: Spark > Issue Type: Improvement > Components: Kubernetes >Affects Versions: 3.4.1 >Reporter: zhuml >Priority: Minor > > Currently the memory request and limit are set by summing the values of > spark.\{driver,executor}.memory and spark.\{driver,executor}.memoryOverhead. > Supporting configurable memory limits can bring some benefits. For example, > use unfixed memory to use page cache, reduce disk IO of shuffle read to > improve performance. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org