[PHOENIX-2163] Measure performance of Phoenix/Calcite querying

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: calcite
• Assignee: Wei Xue
• Reporter: James R. Taylor
• Created: 05/Aug/15 17:03
• Updated: 26/Jan/16 03:48

Description

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

Sub-Tasks

• Add missing scalar function and aggregate function support in Calcite: Open