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

Michael Semb Wever edited comment on CASSANDRA-16079 at 8/28/20, 3:56 PM:
--------------------------------------------------------------------------

The ccm used in each dtest run is from `origin/master`. So pre-bootstrapping 
the parameterised ccm clusters (to create the template/cache), would have to be 
done per overall dtest run. Caching templates for past ccm SHAs doesn't hold a 
lot of value.

It would be _nice_ to introduce the improvement inside dtest+ccm codebases, so 
it's consistently used by all (rather than docker/vm snapshots). 




was (Author: michaelsembwever):
The ccm used in each dtest run is from `origin/master`. So pre-bootstrapping 
the parameterised ccm clusters so to  template/cache, has to be done per 
overall dtest run. Caching templates for past ccm SHAs doesn't hold a lot of 
value.

It would be _nice_ to introduce the improvement inside dtest+ccm codebases, so 
it's consistently used by all (rather than docker/vm snapshots). 



> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to