[
https://issues.apache.org/jira/browse/PHOENIX-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923211#comment-13923211
]
Lars Hofhansl commented on PHOENIX-76:
--------------------------------------
Also checkout this comment:
https://issues.apache.org/jira/browse/HBASE-9811?focusedCommentId=13807622&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13807622
(reseek is faster as the number of HFiles increases)
I am not trying to be the party pooper... Just that the isolated benchmarks
don't do this justice.
> Fix perf regression due to PHOENIX-29
> -------------------------------------
>
> Key: PHOENIX-76
> URL: https://issues.apache.org/jira/browse/PHOENIX-76
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: James Taylor
> Assignee: Anoop Sam John
> Fix For: 3.0.0
>
> Attachments: 76-Hints.patch, PHOENIX-76.patch, patch.diff
>
>
> Many queries got slower as a result of PHOENIX-29. There are a few simple
> checks we can do to prevent the adding of the new filter:
> - if the query is an aggregate query, as we don't return KVs in this case, so
> we're only doing extra processing that we don't need. For this, you can check
> statement.isAggregate().
> - if there are multiple column families referenced in the where clause, as
> the seek that gets done is better in this case because we'd potentially be
> seeking over an entire stores worth of data into a different store.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
