You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hongze Zhang (Jira)" <ji...@apache.org> on 2026/06/10 19:34:00 UTC

[jira] [Updated] (SPARK-57376) Add off-heap broadcast support for shuffle status

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

Hongze Zhang updated SPARK-57376:
---------------------------------
    Summary: Add off-heap broadcast support for shuffle status  (was: Add off-heap broadcasting support for shuffle status)

> Add off-heap broadcast support for shuffle status
> -------------------------------------------------
>
>                 Key: SPARK-57376
>                 URL: https://issues.apache.org/jira/browse/SPARK-57376
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Spark Core
>    Affects Versions: 4.1.2
>            Reporter: Hongze Zhang
>            Priority: Major
>
> The issue:
> When shuffle partition number is configured large, Spark could use significant large amount of JVM heap memory just for storing the broadcasted shuffle status, even with off-heap mode enabled. For fixing this, we can do some minor enhancements around the shuffle status tracker and the base torrent broadcast API. 
>  
> The fix:
> The fix can be split to 2 steps. Step 1 is to optimize against the broadcast blocks to enable off-heap support, and step 2 is to optimize against the broadcast values for the same purpose. Local sanity tests, and memory footprint benchmark can be run for the final verification.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org