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 2020/02/12 10:21:00 UTC

[jira] [Updated] (CALCITE-3785) Performance regression in HepPlanner#belongsToDag() due to expensive hashCode computation

     [ https://issues.apache.org/jira/browse/CALCITE-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stamatis Zampetakis updated CALCITE-3785:
-----------------------------------------
    Summary: Performance regression in HepPlanner#belongsToDag() due to expensive hashCode computation  (was: HepPlanner.belongToDag() doesn't have to use mapDigestToVertex)

> Performance regression in HepPlanner#belongsToDag() due to expensive hashCode computation
> -----------------------------------------------------------------------------------------
>
>                 Key: CALCITE-3785
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3785
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Xiening Dai
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> To test whether or not a vertex belongs to DAG, we can simply do graph.vertexSet().contains(vertex); There's no need to look up in mapDigestToVertex map, which incurs overhead of creating the map key. This problem was amplified by CALCITE-3713.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)