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

ramkrishna.s.vasudevan updated HBASE-21874:
-------------------------------------------
    Status: Patch Available  (was: Open)

Patch seems to be big now due to the refactoring done. Now we have an abstract 
MmapIOEngine with ExclusiveMemoryMMapIOEngine (old FileMMapIOEngine) and 
SharedMemoryMMapIOEngine(PmemIOEngine) are its subclasses. Since both have 
similar mechanisms for mmaping and only the backing device is different which 
helps us in creating a SHARED memory  we went with this approach (so that is 
more abstract in nature). It also answers [~jdcryans] comments. 

[~busbey] - Thanks for pointing out the xmls and doc to be changed. We had 
missed it out. Let us know what you think of the latest patch. 

> Bucket cache on Persistent memory
> ---------------------------------
>
>                 Key: HBASE-21874
>                 URL: https://issues.apache.org/jira/browse/HBASE-21874
>             Project: HBase
>          Issue Type: New Feature
>          Components: BucketCache
>    Affects Versions: 3.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-21874.patch, HBASE-21874.patch, 
> HBASE-21874_V2.patch, HBASE-21874_V4.patch, Pmem_BC.png
>
>
> Non volatile persistent memory devices are byte addressable like DRAM (for 
> eg. Intel DCPMM). Bucket cache implementation can take advantage of this new 
> memory type and can make use of the existing offheap data structures to serve 
> data directly from this memory area without having to bring the data to 
> onheap.
> The patch is a new IOEngine implementation that works with the persistent 
> memory.
> Note : Here we don't make use of the persistence nature of the device and 
> just make use of the big memory it provides.
> Performance numbers to follow. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to