[jira] [Comment Edited] (CASSANDRA-16079) Improve dtest runtime

["Jeremy Hanna (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-16079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197300#comment-17197300 ] 

Jeremy Hanna edited comment on CASSANDRA-16079 at 9/17/20, 12:22 AM:
---------------------------------------------------------------------

Is it possible to implement some sort of "reset" operation in CCM so that it drops all non-system keyspaces so that the clusters that don't explicitly test cluster membership operations can just be reused as has been said?  We could disable snapshotting on them as well so they wouldn't build up state over time too.

In other words, it sounds like if we made the time for starting single node clusters essentially instant, that's 171 * single node startup time that we've reduced for the overall dtests.


was (Author: jeromatron):
Is it possible to implement some sort of "reset" operation in CCM so that it drops all non-system keyspaces so that the clusters that don't explicitly test cluster membership operations can just be reused as has been said?  We could disable snapshotting on them as well so they wouldn't build up state over time too.

> 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
>            Priority: Normal
>             Fix For: 4.0-beta
>
>
> 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