You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "liyang (JIRA)" <ji...@apache.org> on 2017/02/08 07:10:41 UTC

[jira] [Commented] (KYLIN-2325) kylin sql optimization is very slow about 100ms or so, and consumes a lot of cpu

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

liyang commented on KYLIN-2325:
-------------------------------

Hi [~elasticlog], thanks for bring up this topic.

100ms is not much in big data scenario and it's meant to use CPU.

That said, what is your requirement regarding the SQL parsing performance? Why is 100ms a concern? Is it a bottleneck in your env? Any performance goal you want to achieve?

Please share more background.

> kylin sql optimization is very slow about 100ms or so, and consumes a lot of cpu
> --------------------------------------------------------------------------------
>
>                 Key: KYLIN-2325
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2325
>             Project: Kylin
>          Issue Type: Improvement
>            Reporter: WangTaiZe
>              Labels: performance
>             Fix For: v2.0.0
>
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> kylin sql optimization is too slow, and consumes too much cpu. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)