drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jinfeng Ni (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5468) TPCH Q18 regressed ~3x due to execution plan changes
Date Thu, 13 Jul 2017 22:54:00 GMT

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

Jinfeng Ni commented on DRILL-5468:
-----------------------------------

[~amansinha100], thanks. I think Option 1 makes sense for 1.11.

[~dechanggu], can you run tpch Q18, with the following option, and see if you still see the
3X regression or not. 

{code}
alter session set `planner.broadcast_threshold` = 35000000;  // or any value higher than 30M
{code}

> TPCH Q18 regressed ~3x due to execution plan changes
> ----------------------------------------------------
>
>                 Key: DRILL-5468
>                 URL: https://issues.apache.org/jira/browse/DRILL-5468
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Functions - Drill
>    Affects Versions: 1.11.0
>         Environment: 10+1 node ucs-micro cluster RHEL6.4
>            Reporter: Dechang Gu
>            Assignee: Jinfeng Ni
>             Fix For: 1.11.0
>
>         Attachments: Q18_profile_gitid_841ead4, Q18_profile_gitid_adbf363
>
>
> In a regular regression test on Drill master (commit id 841ead4) TPCH Q18 on SF100 parquet
dataset took ~81 secs, while the same query on 1.10.0 took only ~27 secs.  The query time
on the commit adbf363 which is right before 841ead4 is ~32 secs.
> Profiles shows the plans for the query changed quite a bit (profiles will be uploaded)




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message