hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11927) Use Native Hadoop Library for HFile checksum
Date Tue, 12 May 2015 21:51:00 GMT

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

stack commented on HBASE-11927:

Definetly a different profile.

For the 'without' I see hdfs checksum on write taking 4.58% but for the 'with' native, it
takes 8.14%.

Writing the hfiles, I see 'without' taking 8.17% and with native, taking 6.59%.

Reading, without takes 15.59% CPU and with native, it takes 7.39%.

What configs did you run with? Did you enable crc32c?

Patch looks good [~appy]

> Use Native Hadoop Library for HFile checksum
> --------------------------------------------
>                 Key: HBASE-11927
>                 URL: https://issues.apache.org/jira/browse/HBASE-11927
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Apekshit Sharma
>         Attachments: HBASE-11927-v1.patch, HBASE-11927.patch, c2021.crc2.svg, c2021.write.2.svg,
c2021.zip.svg, compact-with-native.svg, compact-without-native.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

View raw message