Hudson commented on HBASE-20564:

Results for branch master
        [build #334 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/334/]: (x) 
*{color:red}-1 overall{color}*
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 

(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 

(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 

(/) {color:green}+1 source release artifact{color}
-- See build output for details.

> Tighter ByteBufferKeyValue Cell Comparator
> ------------------------------------------
>                 Key: HBASE-20564
>                 URL: https://issues.apache.org/jira/browse/HBASE-20564
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Performance
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.0.1
>         Attachments: 0001-HBASE-20564-addendum.txt, 
> 0001-HBASE-20564-addendum.txt, 0001-HBASE-20564-addendum2.branch-2.0.patch, 
> 0002-HBASE-20564-addendum.branch-2.0.patch, 1.4.pe.write.0510.96203.cpu.svg, 
> 2.p3.write2.0514.104236.cpu.svg, 2.pe.write.135142.cpu.svg, 20564.addendum, 
> HBASE-20564.branch-2.0.001.patch, HBASE-20564.branch-2.0.002.patch, 
> HBASE-20564.branch-2.patch, hits.png
> Comparing Cells in hbase2 takes almost 3x the CPU.
> In hbase1, its a keyValue backed by a byte array caching a few important 
> values.. In hbase2, its a NoTagByteBufferChunkKeyValue(?) deserializing the 
> row/family/qualifier lengths repeatedly.
> I tried making a purposed comparator -- one that was not generic -- and it 
> seemed to have a nicer profile coming close to hbase1 in percentage used 
> (I'll post graphs) when I ran it in my perpetual memstore filler (See scripts 
> attached to HBASE-20483). It doesn't work when I try to run it on cluster. 
> Let me run unit tests to see if it can figure what I have wrong.

This message was sent by Atlassian JIRA

Reply via email to