[
https://issues.apache.org/jira/browse/HBASE-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240627#comment-15240627
]
stack commented on HBASE-12148:
-------------------------------
Ok. So, scratching this last patch. It could make lots of objects at read-time
and besides, as [~lhofhansl] says, this issue is about write time, not read
time, which is what I (and [~wkoetke]) are complaining about.
The fix for read time is pretty straight-forward; just use a TimeRange as
opposed to a TimeRangeTracker when reading. See HBASE-15650 for patch.
I'll come back here when doing more write tests; I like the [~wkoetke] patch..
maybe we can do a version for write-time (Chatting w/ our Matteo, he was
suggesting we might be able to reuse the little data structure objects that are
in the [~wkoetke] patch which would be great... )
> 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,
> 12148v4.patch, 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
(v6.3.4#6332)
