[
https://issues.apache.org/jira/browse/IMPALA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757658#comment-17757658
]
Michael Smith commented on IMPALA-5081:
---------------------------------------
[~baggio000] any thoughts on how this should interact with codegen cache? We
could make it part of the key so that if you use a different optimization level
it won't get a cache hit (and run with a potentially slower optimized version).
> Expose IR optimization level via query option
> ---------------------------------------------
>
> Key: IMPALA-5081
> URL: https://issues.apache.org/jira/browse/IMPALA-5081
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Michael Ho
> Assignee: Michael Smith
> Priority: Minor
> Labels: codegen
>
> Certain queries may spend a lot of time in the IR optimization. Currently,
> there is a start-up option to disable optimization in LLVM. However, it may
> be of inconvenience to users to have to restart the entire Impala cluster to
> just use that option. This JIRA aims at exploring exposing a query option for
> users to choose the optimization level for a given query (e.g. we can have a
> level which just only have a dead code elimination pass or no optimization at
> all).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
