[
https://issues.apache.org/jira/browse/PHOENIX-5616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996720#comment-16996720
]
Lars Hofhansl commented on PHOENIX-5616:
----------------------------------------
testToolWithNoIndex seems out of place here. This test tests with a single
table (created as part of that method) and nothing else and is only run in one
of the 4 cases. Nontheless the test is called 4 times, and sets up all the
tables and indexes. We can easily cut a quarter of the test runtime by running
that one separately.
> Speed up ParameterizedIndexUpgradeToolIT and IndexToolIT
> --------------------------------------------------------
>
> Key: PHOENIX-5616
> URL: https://issues.apache.org/jira/browse/PHOENIX-5616
> Project: Phoenix
> Issue Type: Test
> Reporter: Lars Hofhansl
> Priority: Minor
>
> Here're the top 6 longest running tests (times in seconds on a jenkins box
> for a 4.x-HBase-1.5 jobs - other runs are similar):
> 946.612 org.apache.phoenix.end2end.ParameterizedIndexUpgradeToolIT
> 671.655 org.apache.phoenix.end2end.IndexToolIT
> 578.311 org.apache.phoenix.end2end.index.MutableIndexIT
> 573.698 org.apache.phoenix.end2end.SystemCatalogCreationOnConnectionIT
> 508.456 org.apache.phoenix.end2end.index.LocalIndexIT
> 473.577 org.apache.phoenix.end2end.index.ImmutableIndexIT
> ParameterizedIndexUpgradeToolIT is by far the slowest, followed by
> IndexToolIT. And 5 of the 6 slowest tests are related to indexing.
> (This might seem like a trifle, but fast test runtimes are crucial for
> developer productivity.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
