You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2017/02/04 13:40:51 UTC
[jira] [Commented] (KYLIN-2424) Optimize the integration test's
performance
[ https://issues.apache.org/jira/browse/KYLIN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852787#comment-15852787 ]
Shaofeng SHI commented on KYLIN-2424:
-------------------------------------
The change is pushed to master at: https://github.com/apache/kylin/commit/5d83c80fbc0d6c3db434368cc8c29d786eebcd94
Now the ITCombinationTest takes less than 3 minutes in my local.
> Optimize the integration test's performance
> -------------------------------------------
>
> Key: KYLIN-2424
> URL: https://issues.apache.org/jira/browse/KYLIN-2424
> Project: Kylin
> Issue Type: Improvement
> Components: Tools, Build and Test
> Reporter: Shaofeng SHI
> Assignee: Shaofeng SHI
> Fix For: v2.0.0
>
>
> Kylin's integration test is slow, especially the ITCombinationTest. Most of time are spent on H2 to execute the test queries. In a latest integration test, this test case take 90 minutes to finish.
> By checking H2's document, I think the main problem is the absence of index on the tables, while index is very important for a relational database's query performance. So when Kylin create the tables in H2, shoud create index on the columns that will be used in the queries, like the pk/fk, the filtering columns etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)