[
https://issues.apache.org/jira/browse/PHOENIX-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209230#comment-14209230
]
James Taylor commented on PHOENIX-1427:
---------------------------------------
Yes, we don't use min/max key anywhere (and don't need it). All those key
comparisons (which even if we needed the min/max key, aren't necessary as the
data is already sorted), slow down compactions for no reason. We could remove
from system.stats schema too, but let's do that in a minor release. It's not
hurting anything - the table is an internal table and those columns would
always just return null.
> Reduce work in StatsCollector
> -----------------------------
>
> Key: PHOENIX-1427
> URL: https://issues.apache.org/jira/browse/PHOENIX-1427
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: James Taylor
> Attachments: 1427-4.2.txt, PHOENIX-1427.patch
>
>
> I noticed that the StatsCollector does a non-trivial amount of work during
> HBase compactions.
> In a sort of worst case scenario (single node cluster, all data on SSD), it
> adds almost 50% to the compaction time - in a real setup the relative time
> spent there would be much less of course.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
