[
https://issues.apache.org/jira/browse/STORM-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957277#comment-14957277
]
ASF GitHub Bot commented on STORM-1105:
---------------------------------------
Github user haohui commented on the pull request:
https://github.com/apache/storm/pull/796#issuecomment-148118238
The main motivation is performance -- The code that generated by Calcite
has a lot of down casts which can potentially have a visible impact, as the
targeted throughput is millions of messages per seconds.
Bringing LLVM allows StormSQL to leverage the mature optimization and opens
up further opportunities including automatic vectorization, etc.
Note that LLVM is used only for optimization -- the next step is to
translate LLVM IR back to Java Bytecode (STORM-1097). The approach is quite
similar to using Janino to generate Java bytecode. There is no native
components in the worker node.
> Compile the logical plans into LLVM functions
> ---------------------------------------------
>
> Key: STORM-1105
> URL: https://issues.apache.org/jira/browse/STORM-1105
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-sql
> Reporter: Haohui Mai
> Assignee: Haohui Mai
>
> This jira tracks the effort on compiling the stages of the logical plans into
> LLVM functions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
