[
https://issues.apache.org/jira/browse/DRILL-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994875#comment-14994875
]
Jacques Nadeau commented on DRILL-4046:
---------------------------------------
That's crazy, we had this bug two years ago. We're using the wrong date parsing
functions.
[~mehant] rewrote the date casting functions so we didn't rely on Joda time.
Something has caused a regression in the function resolution.
Looking at the commit history, I wonder if this commit caused the regression:
https://github.com/apache/drill/commit/17abf36adf54ef73e151c21497b0fdba9e7864fa
> Performance regression in some tpch queries with 1.3rc0 build
> -------------------------------------------------------------
>
> Key: DRILL-4046
> URL: https://issues.apache.org/jira/browse/DRILL-4046
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Jacques Nadeau
> Assignee: Jacques Nadeau
> Attachments: profiles.tar.gz
>
>
> ||commit/query||14||15||18||20||
> |[839f8da|https://github.com/apache/drill/commit/839f8dac2e2d0479a1552701a5274ebe8416fea6]|10,253|14,642|32,993|21,251|
> |[e7db9dc|https://github.com/apache/drill/commit/e7db9dcacbc39c4797de1aa29b119a7428451dea]|85,061|211,400|900,020|34,066|
> (Time in milliseconds; 900 second timeout)
> + These regressions are not consistent i.e. on multiple runs, some runs do
> not vary from the baseline.
> + TPCH 18 did not regress without timing out (on runs until now).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
