You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Shuxiong Ye (JIRA)" <ji...@apache.org> on 2015/09/09 11:51:45 UTC

[jira] [Updated] (PHOENIX-2163) Measure performance of Phoenix/Calcite querying

     [ https://issues.apache.org/jira/browse/PHOENIX-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shuxiong Ye updated PHOENIX-2163:
---------------------------------
    Attachment: publish.7167262.tar.gz
                hbase-logs.7167262.tar.gz

This is the test result for latest calcite branch(version: 7167262).

------------

In publish.7167262.tar.gz, it will be easy to check all Sql which fail to execute on certain table in "Queries by Table":
1) In AGGREGATION_TABLE, 
select round(date, 'day',50), sum(core)+2 from AGGREGATION_TABLE where (CORE<10 or CORE>90) group by round(date, 'day',50), host
select trunc(date, 'hour', 1000), count(DB), count(ACTIVE_VISITOR) from AGGREGATION_TABLE where feature='Login' and (core<50 or db<20 or active_visitor > 200) group by trunc(date, 'hour', 1000)
select count(active_visitor) count from AGGREGATION_TABLE
select count(distinct active_visitor) count from AGGREGATION_TABLE
select percentile_cont(0.9) within group (order by active_visitor asc) from AGGREGATION_TABLE
select percentile_cont(0.1) within group (order by active_visitor desc) from AGGREGATION_TABLE
select percentile_cont(0.5) within group (order by core asc), percentile_cont(0.5) within group (order by db asc), percentile_cont(0.5) within group (order by active_visitor asc) from AGGREGATION_TABLE
select core, count(db) count from AGGREGATION_TABLE group by CORE
select core, count(distinct db) count from AGGREGATION_TABLE group by CORE
select core, percentile_cont(0.9999) within group (order by db asc) from AGGREGATION_TABLE group by CORE

2) For table INDEXED_TABLE INDEXED_TABLE_MUTABLE  TABLE_6CF SALTED_TABLE TABLE_1CF WIDE_PK, tests all failed to pass. Maybe some features used by tests are not supported by calcite.
The ddl for all these table can be found in result page.

> Measure performance of Phoenix/Calcite querying
> -----------------------------------------------
>
>                 Key: PHOENIX-2163
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2163
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Shuxiong Ye
>         Attachments: PHOENIX-2163.patch, calcite-test-mac.tar.gz, hbase-logs.7167262.tar.gz, publish.7167262.tar.gz
>
>
> The work to integrate Phoenix with Calcite has come along far enough that queries both against the data table and through a secondary index is functional. As a checkpoint, we should compare performance of as many queries as possible in our regression suite for the calcite branch against the latest Phoenix release (4.5.0). The runtime of these two systems should be the same, so this will give us an idea of the overhead of query parsing and compilation for Calcite. This is super important, as it'll identify outstanding work that'll be necessary to do prior to any releases on top of this new stack.
> Source code of regression suite is at https://github.com/mujtabachohan/PhoenixRegressor
> Connection string location: https://github.com/mujtabachohan/PhoenixRegressor/blob/master/src/main/resources/settings.json
> Instructions on how to compile and run: https://github.com/mujtabachohan/PhoenixRegressor/blob/master/README.md



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