[jira] [Updated] (CASSANDRA-16079) Improve dtest runtime

["Michael Semb Wever (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-16079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Semb Wever updated CASSANDRA-16079:
-------------------------------------------
    Fix Version/s:     (was: 4.0.x)
                   4.0-beta

> Improve dtest runtime
> ---------------------
>
>                 Key: CASSANDRA-16079
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16079
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CI
>            Reporter: Adam Holmberg
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 4.0-beta
>
>         Attachments: Screenshot 2020-09-19 at 12.32.21.png
>
>
> A recent ticket, CASSANDRA-13701, changed the way dtests run, resulting in a [30% increase in run time|https://www.mail-archive.com/dev@cassandra.apache.org/msg15606.html]. 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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org