You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "hongbin ma (JIRA)" <ji...@apache.org> on 2017/02/06 13:21:41 UTC
[jira] [Comment Edited] (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=15853970#comment-15853970 ]
hongbin ma edited comment on KYLIN-2424 at 2/6/17 1:20 PM:
-----------------------------------------------------------
[~Shaofengshi] great work!
[~yimingliu] looks like it's abbreviation for "true". If so it could be confusing, why not just use "true"?
was (Author: mahongbin):
[~Shaofengshi] great work! I can close KYLIN-2015 safely now
[~yimingliu] looks like it's abbreviation for "true". If so it could be confusing, why not just use "true"?
> 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)