[ https://issues.apache.org/jira/browse/CASSANDRA-16079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231995#comment-17231995 ]
Michael Semb Wever commented on CASSANDRA-16079: ------------------------------------------------ Taking advantage of CASSANDRA-16205 this patch pre-generates tokens using the allocation strategy (for RF=3). https://github.com/riptano/ccm/compare/cassandra-test...thelastpickle:mck/16205 Those dtests that want the token allocation strategy generation to happen when the node bootstraps can disable it using {code} cluster.set_environment_variable('CASSANDRA_TOKEN_PREGENERATION_DISABLED', True) {code} > 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.x > > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org