You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Adam Holmberg (Jira)" <ji...@apache.org> on 2020/08/27 19:52:00 UTC
[jira] [Comment Edited] (CASSANDRA-16079) Improve dtest runtime
[ https://issues.apache.org/jira/browse/CASSANDRA-16079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186072#comment-17186072 ]
Adam Holmberg edited comment on CASSANDRA-16079 at 8/27/20, 7:51 PM:
---------------------------------------------------------------------
One idea that was relayed (with attribution to [~mck]] and [~blambov]):
{quote}remove the bootstrapping from all dtests that don't need it. e.g. to bootstrap parameterized ccm clusters and save them as templates, and then have each dtest to copy a ccm template and start it up. that deduces sequential bootstrap time with parallel startup time, on basically every dtest.{quote}
was (Author: aholmber):
One idea that was relayed (with attribution to [~mck2] and [~blambov]):
{quote}remove the bootstrapping from all dtests that don't need it. e.g. to bootstrap parameterized ccm clusters and save them as templates, and then have each dtest to copy a ccm template and start it up. that deduces sequential bootstrap time with parallel startup time, on basically every dtest.{quote}
> 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