[
https://issues.apache.org/jira/browse/HBASE-20620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-20620:
------------------------------
Fix Version/s: 2.1.0
3.0.0-alpha-1
> Tighter ByteBufferKeyValue Cell Comparator; part 2
> --------------------------------------------------
>
> Key: HBASE-20620
> URL: https://issues.apache.org/jira/browse/HBASE-20620
> Project: HBase
> Issue Type: Sub-task
> Components: Performance
> Affects Versions: 2.0.0
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.1.0, 2.0.1
>
> Attachments: HBASE-20620.branch-2.0.001.patch,
> HBASE-20620.branch-2.0.002.patch, HBASE-20620.branch-2.0.003.patch, hits.png
>
>
> This is a follow-on from HBASE-20564 "Tighter ByteBufferKeyValue Cell
> Comparator". In this issue, we make a stripped-down comparator that we deploy
> in one location only, as memstore Comparator. HBASE-20564 operated on
> CellComparator/Impl and got us 5-10k more throughput on top of a baseline 40k
> or so. A purposed stripped-down ByteBufferKeyValue comparator that fosters
> better inlining gets us from 45-50k up to about 75k (1.4 does 110-115k no-WAL
> PE writes). Data coming. Log of profiling kept here:
> https://docs.google.com/document/d/1vZ_k6_pNR1eQxID5u1xFihuPC7FkPaJQW8c4M5eA2AQ/edit#
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
