[
https://issues.apache.org/jira/browse/HADOOP-16415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887449#comment-16887449
]
Steve Loughran commented on HADOOP-16415:
-----------------------------------------
The {{ITestAssumedRoleCommitOperations}} is pretty slow and it just runs
ITestCommitOperations under an assumed role.
* we could make this the default behaviour if he assumed role option is set.
The commit protocol tests are all critical, maybe we could combine some tests
into something longer. Risk of higher maintenance tho'.
ITestS3GuardConcurrentOps should be converted to a scale test
The 60s for the SSE-C encryption test {{ITestS3AEncryptionSSEC}} is
particularly painful, given SSE-C isn't used much, and it adds 60s to a test
run. It doesn't to much, but we can't parallelize it or it screws up everything
else. Maybe we could merge the tests, but if there's an overhead with every
test case, it has to be create/destroy of every S3A instance.
> Speed up S3A test runs
> ----------------------
>
> Key: HADOOP-16415
> URL: https://issues.apache.org/jira/browse/HADOOP-16415
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Priority: Major
>
> S3A Test runs are way too slow.
> Speed them by
> * reducing test setup/teardown costs
> * eliminating obsolete test cases
> * merge small tests into larger ones.
> One thing i see is that the main S3A test cases create and destroy new FS
> instances; There's both a setup and teardown cost there, but it does
> guarantee better isolation.
> Maybe if we know all test cases in a specific suite need the same options, we
> can manage that better; demand create the FS but only delete it in an
> @Afterclass method. That'd give us the OO-inheritance based setup of tests,
> but mean only one instance is done per suite
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
