[
https://issues.apache.org/jira/browse/HBASE-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132533#comment-14132533
]
stack commented on HBASE-11927:
-------------------------------
Thanks for the pointer [~tlipcon]. Had been thinking to switch over to
DataChecksum and use its verifyChunkedSums but I see it is private, and yeah,
wants checksums as a side dish. It looks like there maybe 20% CPU or more to be
had if could use the native implementations.
bq. BTW, when I tried to use the zlib crc in Java7 I found it wasn't any faster
than Java6.
Coarse testing showed no difference. The flame graphs show about same amount
of cpu consumption, maybe slightly less, and about same elapsed time.
> If java7, use zip crc
> ---------------------
>
> Key: HBASE-11927
> URL: https://issues.apache.org/jira/browse/HBASE-11927
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Fix For: 0.99.1
>
> Attachments: 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)
