You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2019/06/18 21:52:00 UTC

[jira] [Comment Edited] (PHOENIX-5355) Speed up BaseIndexIT

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

Lars Hofhansl edited comment on PHOENIX-5355 at 6/18/19 9:51 PM:
-----------------------------------------------------------------

2. testMaxIndexesPerTable likewise makes no differentiation between tables and index types.

This is the worst offender indeed. It simply creates as many indexes as are allowed, which can take a long time. I think we can only do this once as there's no difference in the metadata handling between the indexes.
In fact I wonder about the utility of this test generally.


was (Author: lhofhansl):
2. testMaxIndexesPerTable likewise makes no differentiation between tables and index types.

> Speed up BaseIndexIT
> --------------------
>
>                 Key: PHOENIX-5355
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5355
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Lars Hofhansl
>            Priority: Major
>
> These are now the slowest tests we have.
> {code:java}
> [INFO] Tests run: 84, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,062.475 s - in org.apache.phoenix.end2end.index.GlobalMutableNonTxIndexWithLazyPostBatchWriteIT
> [INFO] Tests run: 84, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,051.66 s - in org.apache.phoenix.end2end.index.GlobalMutableNonTxIndexIT{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)