[
https://issues.apache.org/jira/browse/CASSANDRA-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008351#comment-14008351
]
Lyuben Todorov commented on CASSANDRA-6968:
-------------------------------------------
My plan is to first allow all the tests to define their own schema rather than
creating every possible KS / CF required by the entire suite. The next step is
to only start gossip where necessary. I've pushed a
[commit|https://github.com/lyubent/cassandra/commit/82381959809012ad7036bca9d84ddda24f0cb862]
demoing the idea with the BatchlogManagerTest and how it only creates the 1ks
/ 3 cfs it needs. This saves aprox 2sec on my machine (previously 3800ms to
create the schema, now 1600ms)
> 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)
