[
https://issues.apache.org/jira/browse/HBASE-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-12148:
--------------------------
Attachment: Screen Shot 2016-04-13 at 1.49.30 PM.png
Screen Shot 2016-04-13 at 2.02.22 PM.png
+1 on this last patch. I like the AtomicReference trick. Nice.
I ran into this issue again while profiling. The TimeRangeTracker is reported
as the location where we contend most in a ycsb workloadc randomread test doing
about 300k ops a second.
Attached are flight recorder before and after where TimeRangeTracker goes from
being most contended item to not showing at all.
Let me reattach patch and get a clean build then will apply everywhere.
> 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
(v6.3.4#6332)
