[
https://issues.apache.org/jira/browse/HBASE-20620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488392#comment-16488392
]
Hudson commented on HBASE-20620:
--------------------------------
Results for branch branch-2.0
[build #340 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/340/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/340//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/340//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/340//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> 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: stack
> Assignee: stack
> Priority: Major
> Fix For: 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
(v7.6.3#76005)
