[
https://issues.apache.org/jira/browse/HBASE-13307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375475#comment-14375475
]
stack commented on HBASE-13307:
-------------------------------
@anoop No seeks. No L2. All in block cache or os cache.
[~lhofhansl]
bq. Do you see real end-to-end time improvements?
Hard to tell. My graphs on mean and median are a little erratic from this time.
They show the two runs about the same with the more throughput run maybe higher
latency but too erratic to be trusted. Could do longer runs to see if they
stabilize better.
> Making methods under ScannerV2#next smaller allows them to be inlined gaining
> us 7% more throughput
> ---------------------------------------------------------------------------------------------------
>
> Key: HBASE-13307
> URL: https://issues.apache.org/jira/browse/HBASE-13307
> Project: HBase
> Issue Type: Sub-task
> Components: Scanners
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.1.0
>
> Attachments: 13307.txt, traces.8.svg, traces.9.svg
>
>
> See parent issue for patch and evidence.
> I was looking at graphs of our scan and found that methods were 'too big' to
> be inlined (looking at jvm compilation and inlining output flags -- see
> parent for list). Changing method size helped some. Let me commit the
> resultant patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
