[CASSANDRA-16079] Improve dtest runtime

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta4, 4.0
• Component/s: CI
• Change Category: Quality Assurance
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/riptano/ccm/commit/d8b0e554e5c5c22644fd90f4152cc825dfed7f1b https://github.com/apache/cassandra-dtest/commit/7ba3bdd88cce56c0bf33b3288e2de3a9a241b5c4

Test and Documentation Plan

CI pass rate and run times, after CASSANDRA-16205 is committed.

• Assignee: Michael Semb Wever
• Reporter: Adam Holmberg

Authors

Michael Semb Wever

Reviewers

Adam Holmberg, Paulo Motta

• Created: 27/Aug/20 19:21
• Updated: 16/Dec/20 17:11
• Resolved: 16/Dec/20 17:11

Description

A recent ticket, CASSANDRA-13701, changed the way dtests run, resulting in a 30% increase in run time. While that change was accepted, we wanted to spin out a ticket to optimize dtests in an attempt to gain back some of that runtime.

At this time we don't have concrete improvements in mind, so the first order of this ticket will be to analyze the state of things currently, and try to ascertain some valuable optimizations. Once the problems are understood, we will break down subtasks to divide the work.

Some areas to consider:

• cluster reuse
• C* startup optimizations
• Tests that should be ported to in-JVM dtest or even unit tests

Issue Links

• is related to: CASSANDRA-13701 Lower default num_tokens