hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12116) Hot contention spots; writing
Date Tue, 14 Apr 2015 14:53:13 GMT

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

Andrew Purtell commented on HBASE-12116:
----------------------------------------

bq. CRC and unsafe compareto at 20% each
Assumed this is with HBase doing its own checksumming. If we know we have DFSInputStream#read
variants that accept BBs (and zero copy read under the covers), then we could move all reads
over to this interface, check if Hadoop's native CRC (HADOOP-10838) is available to us, and
if so run it over the contents of the BBs we get from HDFS? We'd need 2.6.0 as the floor of
Hadoop support so maybe do this in trunk for 2.0? 

> Hot contention spots; writing
> -----------------------------
>
>                 Key: HBASE-12116
>                 URL: https://issues.apache.org/jira/browse/HBASE-12116
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>         Attachments: 12116.checkForReplicas.txt, 12116.stringify.and.cache.scanner.maxsize.txt,
12116.txt, Screen Shot 2014-09-29 at 5.12.51 PM.png, Screen Shot 2014-09-30 at 10.39.34 PM.png,
Screen Shot 2015-04-13 at 2.03.05 PM.png, perf.write3.svg, perf.write4.svg
>
>
> Playing with flight recorder, here are some write-time contentious synchronizations/locks
(picture coming)



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

Mime
View raw message