hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12148) Remove TimeRangeTracker as point of contention when many threads writing a Store
Date Fri, 18 Mar 2016 04:12:33 GMT

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

Lars Hofhansl commented on HBASE-12148:
---------------------------------------

Do we see actual contention, as in threads waiting for each other? Or is this slow down due
to memory barrier implied by a synchronized (and lock, and CAS, and volatile, and AtomicXXX,
etc)?

[~stack], [~wkoetke], where does this show as a problem? It is at the time when write a store
file? Or is it at the time when we insert into the memstore?


> Remove TimeRangeTracker as point of contention when many threads writing a Store
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-12148
>                 URL: https://issues.apache.org/jira/browse/HBASE-12148
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Performance
>    Affects Versions: 2.0.0, 0.99.1
>            Reporter: stack
>            Assignee: Walter Koetke
>             Fix For: 2.0.0, 1.3.0, 0.98.19
>
>         Attachments: 0001-In-AtomicUtils-change-updateMin-and-updateMax-to-ret.patch,
12148.addendum.txt, 12148.txt, 12148.txt, 12148v2.txt, 12148v2.txt, HBASE-12148-V3.patch,
HBASE-12148.txt, HBASE-12148V2.txt, Screen Shot 2014-10-01 at 3.39.46 PM.png, Screen Shot
2014-10-01 at 3.41.07 PM.png
>
>




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

Mime
View raw message