Anoop Sam John commented on HBASE-11425:
On read path off heaping doc in out book, not many new things are required.
There is nothing much new to be configured by user. The bucket cache off heap
mode was there before also. All the changes were very internal only. Ya we
need to make sure the Bucket cache usage related stuff in book is up to date
and with a highlight for using the off heap mode more. It is even better than
the on heap cache (Old days we called it the L1 cache).. I think some changes
we did as part of some of the jiras. Need to verify again.
On write path yes, some new info to be written. Let me raise some jiras for
> Cell/DBB end-to-end on the read-path
> Key: HBASE-11425
> URL: https://issues.apache.org/jira/browse/HBASE-11425
> Project: HBase
> Issue Type: Umbrella
> Components: regionserver, Scanners
> Affects Versions: 0.99.0
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Priority: Major
> Fix For: 2.0.0
> Attachments: BenchmarkTestCode.zip, Benchmarks_Tests.docx, GC pics
> with evictions_4G heap.png, HBASE-11425-E2E-NotComplete.patch,
> HBASE-11425.patch, Offheap reads in HBase using BBs_V2.pdf, Offheap reads in
> HBase using BBs_final.pdf, Screen Shot 2015-10-16 at 5.13.22 PM.png, gc.png,
> gets.png, heap.png, load.png, median.png, ram.log
> Umbrella jira to make sure we can have blocks cached in offheap backed cache.
> In the entire read path, we can refer to this offheap buffer and avoid onheap
> The high level items I can identify as of now are
> 1. Avoid the array() call on BB in read path.. (This is there in many
> classes. We can handle class by class)
> 2. Support Buffer based getter APIs in cell. In read path we will create a
> new Cell with backed by BB. Will need in CellComparator, Filter (like SCVF),
> CPs etc.
> 3. Avoid KeyValue.ensureKeyValue() calls in read path - This make byte copy.
> 4. Remove all CP hooks (which are already deprecated) which deal with KVs.
> (In read path)
> Will add subtasks under this.
This message was sent by Atlassian JIRA