[
https://issues.apache.org/jira/browse/HBASE-15971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15971:
--------------------------
Attachment: handlers.fp.png
Handlers are erratic still but the peaks are higher. When the q backs up, the
peaks fall as though as though we are 'off' the fast path. Seems sensitive to
amount of Readers. If 6 as is in this case, then we go fast. If 12, we slow
down. Seems like the Readers also act as a bit of bottleneck which means the
Handlers get to go the fast path more often. If I drive even more load, ops go
up to 320k. 15% idle so there is more to be had here.
Work still to do.
> Regression: Random Read/WorkloadC slower in 1.x than 0.98
> ---------------------------------------------------------
>
> Key: HBASE-15971
> URL: https://issues.apache.org/jira/browse/HBASE-15971
> Project: HBase
> Issue Type: Sub-task
> Components: rpc
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Attachments: 098.hits.png, 098.png, HBASE-15971.branch-1.001.patch,
> branch-1.hits.png, branch-1.png, handlers.fp.png, hits.fp.png
>
>
> branch-1 is slower than 0.98 doing YCSB random read/workloadC. It seems to be
> doing about 1/2 the throughput of 0.98.
> In branch-1, we have low handler occupancy compared to 0.98. Hacking in
> reader thread occupancy metric, is about the same in both. In parent issue,
> hacking out the scheduler, I am able to get branch-1 to go 3x faster so will
> dig in here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
