Details
-
Story
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Memory management in Spark is currently broken down into two disjoint regions: one for execution and one for storage. The sizes of these regions are statically configured and fixed for the duration of the application.
There are several limitations to this approach. It requires user expertise to avoid unnecessary spilling, and there are no sensible defaults that will work for all workloads. As a Spark user, I want Spark to manage the memory more intelligently so I do not need to worry about how to statically partition the execution (shuffle) memory fraction and cache memory fraction. More importantly, applications that do not use caching use only a small fraction of the heap space, resulting in suboptimal performance.
Instead, we should unify these two regions and let one borrow from another if possible.
Attachments
Attachments
1.
|
Introduce common memory management interface for execution and storage |
|
Resolved | Andrew Or |
2.
|
Implement unified memory manager |
|
Resolved | Andrew Or |
3.
|
Simplify *MemoryManager class structure |
|
Resolved | Josh Rosen |
4.
|
Ensure spilling tests are actually spilling |
|
Resolved | Andrew Or |
5.
|
Document new memory management model |
|
Resolved | Andrew Or |