[ 
https://issues.apache.org/jira/browse/HBASE-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143358#comment-15143358
 ] 

stack commented on HBASE-11927:
-------------------------------

Backport looks good to me. You'll need to call out in any release the flip to 
CRC32C (it won't be a problem but a change). Its a nice boost so worth the 
backport.

> Use Native Hadoop Library for HFile checksum (And flip default from CRC32 to 
> CRC32C)
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-11927
>                 URL: https://issues.apache.org/jira/browse/HBASE-11927
>             Project: HBase
>          Issue Type: Improvement
>          Components: Performance
>            Reporter: stack
>            Assignee: Appy
>             Fix For: 2.0.0, 1.2.0, 1.1.4
>
>         Attachments: HBASE-11927-branch-1.1.patch, HBASE-11927-v1.patch, 
> HBASE-11927-v2.patch, HBASE-11927-v4.patch, HBASE-11927-v5.patch, 
> HBASE-11927-v6.patch, HBASE-11927-v7.patch, HBASE-11927-v8.patch, 
> HBASE-11927-v8.patch, HBASE-11927.patch, after-compact-2%.svg, 
> after-randomWrite1M-0.5%.svg, before-compact-22%.svg, 
> before-randomWrite1M-5%.svg, c2021.crc2.svg, c2021.write.2.svg, 
> c2021.zip.svg, crc32ct.svg
>
>
> Up in hadoop they have this change. Let me publish some graphs to show that 
> it makes a difference (CRC is a massive amount of our CPU usage in my 
> profiling of an upload because of compacting, flushing, etc.).  We should 
> also make use of native CRCings -- especially the 2.6 HDFS-6865 and ilk -- in 
> hbase but that is another issue for now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to