[
https://issues.apache.org/jira/browse/PHOENIX-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709818#comment-14709818
]
Maryann Xue commented on PHOENIX-2163:
--------------------------------------
Thanks [~shuxi0ng] for the initial results! Could you please post them along
with the error logs on this JIRA?
Meanwhile it would be useful to add "explain plan" check to make sure that each
query runs with a pure Phoenix plan instead of a Enumerable-Phoenix plan. It
might also make sense to test the query compilation time by running "explain
plan".
> 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
>
>
> 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)
