[ https://issues.apache.org/jira/browse/CASSANDRA-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014025#comment-14014025 ]
Lyuben Todorov commented on CASSANDRA-6968: ------------------------------------------- Added the patches and tried to move to {{forkmode="once"}}, branch is first two patches from 7327, with the addition of the static creation of the schema in {{SchemaLoader}}. But even with the cleaning up (via invalidate and rm of sstables) the tests seem to be [unhappy|https://gist.github.com/lyubent/2e50916de08bd23eadd8]. I'm not sure if avoiding multiple schema creations will be faster than avoiding invalidation of {{CFS}} and then removing their sstables. For now I'll redo the patch with Tyler's ideas and add in the avoid-gossiping patch of [CASSANDRA-7327|CASSANDRA-7327] (should be trivial) so we can check if avoiding the need to clear the schema is worth it. > Reduce Unit Test Times Due to Schema Loading > -------------------------------------------- > > Key: CASSANDRA-6968 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6968 > Project: Cassandra > Issue Type: Test > Components: Tests > Reporter: Tyler Hobbs > Assignee: Lyuben Todorov > Priority: Minor > Fix For: 2.1.1 > > > Unit tests which extend SchemaLoader take about 6s longer to run than the > others, on average. We could greatly reduce the time it takes to run the > tests by improving this. > None of the tests require everything that SchemaLoader does. We should > change SchemaLoader into a set of test utilities that are run as needed in > {{\@BeforeClass}} and {{\@AfterClass}} methods. Additionally, instead of > running a full cleanup, most tests could simply use a keyspace or column > family with a unique name (class/method name or perhaps class/method name + > timestamp). -- This message was sent by Atlassian JIRA (v6.2#6252)