[jira] [Commented] (DRILL-1155) Add option to use JDK compiler and use it for runtime generated code over a certain threshold

["Aditya Kishore (JIRA)" <ji...@apache.org>]

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

Aditya Kishore commented on DRILL-1155:
---------------------------------------

With this patch, the user has option to switch between one of the three modes, viz DEFAULT, JDK and JANINO. This can be set by issueing the following SQL against a Drill cluster.

{{alter session set `exec.java_compiler`='*_option_*'}}

This will affect only the current session.

The default behavior is to use Janino compiler for generated source code of less than 256KB and switch to JDK compiler for code larger than this.

> Add option to use JDK compiler and use it for runtime generated code over a certain threshold
> ---------------------------------------------------------------------------------------------
>
>                 Key: DRILL-1155
>                 URL: https://issues.apache.org/jira/browse/DRILL-1155
>             Project: Apache Drill
>          Issue Type: Sub-task
>          Components: Execution - Codegen
>    Affects Versions: 1.0.0-BETA1
>            Reporter: Aditya Kishore
>            Assignee: DrillCommitter
>             Fix For: 1.0.0-BETA1
>
>         Attachments: DRILL-1155-Add-option-to-use-JDK-compiler-and-use-it.patch
>
>
> This is related to DRILL-1095 however it would not completely resolve the issue since the Java class file format enforces a maximum limit of 64K on a code unit.
> However, it does provide some additional headroom as JDK compiler seems to generate slightly smaller bytecode compared to Janino and seems to be faster for source code sizes over a threshold (approximately 256K in my tests). For smaller source code Janino is order of magnitude faster than JDK compiler.



--
This message was sent by Atlassian JIRA
(v6.2#6252)