You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stamatis Zampetakis (JIRA)" <ji...@apache.org> on 2019/05/18 12:39:00 UTC
[jira] [Commented] (CALCITE-3071) Cache the whole sql plan to
reduce the latency and improve the performance
[ https://issues.apache.org/jira/browse/CALCITE-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843148#comment-16843148 ]
Stamatis Zampetakis commented on CALCITE-3071:
----------------------------------------------
I think it makes sense to cache more aggressively but it is not straightforward where is the most appropriate place and what exactly to keep inside. There are many use-cases for Calcite so it is tricky to find the ideal place to put it. Having an initial proposal may help advance the discussion.
> Cache the whole sql plan to reduce the latency and improve the performance
> --------------------------------------------------------------------------
>
> Key: CALCITE-3071
> URL: https://issues.apache.org/jira/browse/CALCITE-3071
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.19.0
> Reporter: Lai Zhou
> Priority: Major
>
> In real business, when sql queries become complex, the overhead of sql plan will increase quickly , and many of the sql queries are duplicates.
> We already have some caching issue about improving the performance, such as the issue
> https://issues.apache.org/jira/browse/CALCITE-2703,
> which reduce code generation and class loading overhead when executing queries in the EnumerableConvention, but I think it's not enough.
> I propose to cache the whole sql plan to reduce the latency ，for the same sql
> , ignoring the cost optimizing based on statistics here, we can cache the generated code for it.
> I use the FrameworkConfig API to execute sql queries, in this way I can easily do this job .
> but it's not easy to make a whole sql execution plan(that says code-gen) cache in the sql processing flow based on JDBC Connection, because there're many intermediate state in this processing flow.
>
> Let's discuss this feature and the probable solutions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)