[ https://issues.apache.org/jira/browse/HBASE-21874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784692#comment-16784692 ]
ramkrishna.s.vasudevan commented on HBASE-21874: ------------------------------------------------ bq.ExclusiveMemoryMmapIOEngine extends from FileMmapIOEngine which returns true, so it is needed. [~busbey] - Added that usesSharedMemory to return false for just being explicit. But as [~wchevreuil] said since FileMMapIOEngine is implementing IOEngine interface by default it is false. So we can avoid that too in ExclusiveMemoryMmapIOEngine. > 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, HBASE-21874_V5.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)