[
https://issues.apache.org/jira/browse/PHOENIX-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153633#comment-14153633
]
Lars Hofhansl commented on PHOENIX-1292:
----------------------------------------
I can no longer reproduce the difference. In fact I get a *completely*
different pattern now. (Latest Phoenix)
This is the same table shape (5 int column, of them the key). 55m rows this
time.
|select distinct(v1) from x where v1 = 1 |46s|
|select distinct(v1) from x where v1 <> 1 |26s|
|select count(\*) from x where v1 <> 1 |21s|
|select count(\*) from x where v1 = 1 |19s|
I had to fiddle with the regions and split them to get then to be an equal
size. I would have expected the guide posts would have spared me that work.
So at least this needs some more investigation.
> Some queries that filter all rows are slow.
> -------------------------------------------
>
> Key: PHOENIX-1292
> URL: https://issues.apache.org/jira/browse/PHOENIX-1292
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
>
> Sorry for the vague title.
> As mentioned PHOENIX-1281, I have seen some runtime anomalies for queries
> that should take similar amounts of time.
> 40m row tables, 4 integer column + integer key. All columns (except keys set
> to 1)
> |select distinct(v1) from x where v1 = 1 |21s|
> |select distinct(v1) from x where v1 <> 1 |50s|
> |select count(\*) from x where v1 <> 1 |45s|
> |select count(\*) from x where v1 = 1 |9.5s|
> Interestingly the queries that filter all rows are 5x slower.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
