[
https://issues.apache.org/jira/browse/HBASE-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186342#comment-15186342
]
Lars Hofhansl commented on HBASE-15431:
---------------------------------------
The load I ran was a Phoenix count\(*) query. Note that almost all interesting
methods using during scanning are _not_ inlined.
* SQM.match
* StoreScanner.next
* HRegion$RegionScannerImpl::nextInternal
* HFileReaderV2$ScannerV2::blockSeek
* FastDiffDeltaEncoder$1::decode
* etc
As said, increasing -XX:FreqInlineSize did not improve things. Presumably
because now too much stuff is being inlined.
> A bunch of methods are hot and too big to be inline
> ---------------------------------------------------
>
> Key: HBASE-15431
> URL: https://issues.apache.org/jira/browse/HBASE-15431
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Attachments: hotMethods.txt
>
>
> I ran HBase with "-XX:+PrintCompilation -XX:+UnlockDiagnosticVMOptions
> -XX:+PrintInlining" and then looked for "hot method too big" log lines.
> I'll attach a log of those messages.
> I tried to increase -XX:FreqInlineSize to 1010 to inline all these methods
> (as long as they're hot, but actually didn't see any improvement).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
