You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Alessandro Solimando (Jira)" <ji...@apache.org> on 2025/03/23 07:27:00 UTC

[jira] [Commented] (CALCITE-6907) Optimize HepPlanner latency for large plan

    [ https://issues.apache.org/jira/browse/CALCITE-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937675#comment-17937675 ] 

Alessandro Solimando commented on CALCITE-6907:
-----------------------------------------------

[~wenzhuang.zwz] thanks for bringing up the topic, it seems interesting but from the look of it, I think it will require broader discussion in the ML and surely more details/discussion here before starting the implementation.

> Optimize HepPlanner latency for large plan
> ------------------------------------------
>
>                 Key: CALCITE-6907
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6907
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Wenzhuang Zhu
>            Priority: Major
>
> HepPlanner cannot quickly optimize plan with 10K+ rel nodes.
> We can improve it by:
> 1.HepPlanner support graph reuse for different HepProgram.
> 2.Don't do eager graph gc, e.g. for listener and graph iterator.
> 3.Use large plan friendly graph iterator.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)