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 Wed, 13 Apr 2016 22:03:27 GMT

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

Lars Hofhansl commented on HBASE-12148:

I still don't get what the problem is. There could be two issues:
# We have actual thread contention, i.e. threads sleeping, waiting on other threads.
# There is no contention, but the memory barriers caused by synchronized (or AtomicXXX or
volatile) cause too much of a slow down.

And does this happen upon _read_ or _write_? We've had issues with this during writes as indicated
in the title of this jira, but now this seems to be about reads (by what [~jleach] says).

With this patch we're creating a new object each time we need to set update the TS, on that
write side (compaction, etc) that could kill us.

> 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-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, Screen Shot 2016-04-13 at 1.49.30 PM.png,
Screen Shot 2016-04-13 at 2.02.22 PM.png, TimeRangeTracker.tiff

This message was sent by Atlassian JIRA

View raw message