GitHub user JoshRosen opened a pull request:

    https://github.com/apache/spark/pull/11942

    [SPARK-14135] Add off-heap storage memory bookkeeping support to 
MemoryManager

    This patch extends Spark's `UnifiedMemoryManager` to add bookkeeping 
support for off-heap storage memory, an requirement for enabling off-heap 
caching (which will be done by #11805). The `MemoryManager`'s 
`storageMemoryPool` has been split into separate on- and off-heap pools and the 
storage and unroll memory allocation methods have been updated to accept a 
`memoryMode` parameter to specify whether allocations should be performed on- 
or off-heap.
    
    In order to reduce the testing surface, the `StaticMemoryManager` does not 
support off-heap caching (we plan to eventually remove the 
`StaticMemoryManager`, so this isn't a significant limitation).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/JoshRosen/spark 
off-heap-storage-memory-bookkeeping

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/11942.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #11942
    
----
commit 86c8a493d3ca580db7a707fbdc326eb37d4f1c94
Author: Josh Rosen <[email protected]>
Date:   2016-03-24T17:29:58Z

    Add memoryMode method to StorageLevel

commit 69e22fe86a1c6c4b138631dfc789d08e47ef094e
Author: Josh Rosen <[email protected]>
Date:   2016-03-17T01:44:20Z

    Add separate on- and off-heap storage memory pools to MemoryManager

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to