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

Michael Semb Wever commented on CASSANDRA-16079:
------------------------------------------------

New round with 
[ccm:f782b17|https://github.com/thelastpickle/ccm/commit/f782b178e85bf9d37d9754400420f80a41933c9d]
 and 
[cassandra-dtest:391709d|https://github.com/apache/cassandra-dtest/commit/391709d4a9bbfbc89672c18758ca802df4b3fa17]:
 - 
[2.2|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-dtest/276/]
 - [3.0|https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/275/]
 - [3.11|https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/273/]
 - [3.11 
novnode|https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest-novnode/38/]
 - [trunk|https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest/274/]
 - [trunk 
novnode|https://ci-cassandra.apache.org/job/Cassandra-devbranch-dtest-novnode/39/]



> 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/[email protected]/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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to