phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3560) Aggregate query performance is worse with encoded columns for schema with large number of columns
Date Wed, 11 Jan 2017 02:33:58 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816912#comment-15816912
] 

Samarth Jain commented on PHOENIX-3560:
---------------------------------------

[~mujtabachohan], it would be interesting to see the performance for encoded immutable tables
with lesser number of columns. We should probably be using different column families beyond
a certain threshold of number of columns.

> Aggregate query performance is worse with encoded columns for schema with large number
of columns
> -------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3560
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3560
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Mujtaba Chohan
>            Assignee: Thomas D'Silva
>             Fix For: 4.10.0
>
>         Attachments: DataGenerator.java, PHOENIX-3565.patch
>
>
> Schema with 5K columns
> {noformat}
> create table (k1 integer, k2 integer, c1 varchar ... c5000 varchar CONSTRAINT PK PRIMARY
KEY (K1, K2)) 
> VERSIONS=1, MULTI_TENANT=true, IMMUTABLE_ROWS=true
> {noformat}
> In this test, there are no null columns and each column contains 200 chars i.e. 1MB of
data per row.
> Count * aggregation is about 5X slower with encoded columns when compared to table non-encoded
columns using the same schema.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message