[
https://issues.apache.org/jira/browse/HBASE-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-11767:
----------------------------------
Attachment: 11767.txt
Not pretty (because I cannot change the API in 0.94).
Exploits the fact that we pass {{SchemaMetrics.METRIC_NEXTSIZE}} through the
layers and hence uses identify to check that and then prebuild the metric name
for the duration of the scanner.
> [0.94] Unnecessary garbage produced by schema metrics during scanning
> ---------------------------------------------------------------------
>
> Key: HBASE-11767
> URL: https://issues.apache.org/jira/browse/HBASE-11767
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.94.23
>
> Attachments: 11767.txt
>
>
> Near the end of StoreScanner.next(...) we find this gem:
> {code}
> } finally {
> if (cumulativeMetric > 0 && metric != null) {
> RegionMetricsStorage.incrNumericMetric(this.metricNamePrefix + metric,
> cumulativeMetric);
> }
> }
> {code}
> So, for each row generated we build up a new metric string, that will be
> identical for each invocation of the StoreScanner anyway (a store scanner is
> valid for at most one region and one operation).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
