[
https://issues.apache.org/jira/browse/PHOENIX-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712572#comment-14712572
]
Shuxiong Ye commented on PHOENIX-2163:
--------------------------------------
calcite-test-mac/*.out contains the explain information.
Take query=select count\(*\) from AGGREGATION_TABLE for example,
in 4.5.0-calcite.out, line 20-22 is the explain information.
{code}
14 Starting gathering stats for AGGREGATION_TABLE ...
15 EXECUTING DDL: update statistics AGGREGATION_TABLE
16 EXECUTING DDL finished
17 runQuery query=select count(*) from AGGREGATION_TABLE
18 select count(*) from AGGREGATION_TABLE - time:[2150, 2220, 3399]
19 getExplainPlan query= EXPLAIN PLAN FOR select count(*) from
AGGREGATION_TABLE
20 EXPLAIN: PhoenixToEnumerableConverter
21 PhoenixServerAggregate(group=[{}], EXPR$0=[COUNT()])
22 PhoenixTableScan(table=[[phoenix, AGGREGATION_TABLE]])
{code}
while in 4.5.1-HBase-1.1.out, line 16-18 is the explain information.
{code}
13 Starting gathering stats for AGGREGATION_TABLE ...
14 EXECUTING DDL: update statistics AGGREGATION_TABLE
15 select count(*) from AGGREGATION_TABLE - time:[1679, 2690, 3091]
16 EXPLAIN: CLIENT 3-CHUNK PARALLEL 1-WAY FULL SCAN OVER AGGREGATION_TABLE
17 SERVER FILTER BY FIRST KEY ONLY
18 SERVER AGGREGATE INTO SINGLE ROW
{code}
Are these the explaining you need?
> 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
>
>
> 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)
