You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2023/02/14 12:12:00 UTC
[jira] [Updated] (IGNITE-18748) Sql. Planner optimization for JOIN. Benchmarks
[ https://issues.apache.org/jira/browse/IGNITE-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-18748:
-----------------------------------------
Labels: ignite-3 (was: )
> Sql. Planner optimization for JOIN. Benchmarks
> ----------------------------------------------
>
> Key: IGNITE-18748
> URL: https://issues.apache.org/jira/browse/IGNITE-18748
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
>
> We have an issue with long query planning for queries with a few joins. Unfortunately, it is just our feeling and we don't have real understanding of performance.
> So, to have a real picture we should have the ability to run some benchmarks and use it to evaluate any changes which could lead to increasing or decreasing planning time.
> Let's have a look at third-party tests which could use real-life queries, e.g. TPCH, and snatch some set of the queries for our mini benchmark. Also will need to provide some explanation why we use a concrete set of queries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)