[
https://issues.apache.org/jira/browse/CASSANDRA-16079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198710#comment-17198710
]
Michael Semb Wever commented on CASSANDRA-16079:
------------------------------------------------
{quote}They are…
- dtest.materialized_views_test (64m)
- dtest.replica_side_filtering_test (54m)
- dtest.repair_tests.repair_test (48m)
- dtest.auth_test (38m)
- dtest.disk_balance_test (34m)
- dtest.cqlsh_tests.test_cqlsh_copy (31m)
- dtest.paging_test (27m)
- dtest.repair_tests.incremental_repair_test (21m)
- dtest.compaction_test (19m){quote}
This breakdown wasn't of any value. DTest CI splits is already happening at the
method level.
Looking at ci-cassandra.a.o (which splits only on round-robin, rather than
timings-based), the splits cover a duration range from ~5 to ~20 minutes.
Looking at those upper range splits I can see that there's a few dtest test
methods taking more than two minutes, but I can't see how addressing them is
going to have any reasonable ROI for overall dtests runtime.
- dtest.repair_tests.repair_test.TestRepair.test_dc_repair (6m38s)
- dtest.repair_tests.repair_test.TestRepair.test_simple_sequential_repair
(4m05s)
-
dtest.materialized_views_test.TestMaterializedViews.test_interrupt_build_process
(3m52s)
- dtest.bootstrap_test.TestBootstrap.test_cleanup (2m44s)
- dtest.replace_address_test.TestReplaceAddress.test_multi_dc_replace_with_rf1
(2m14s)
I was hoping that the timings would be visible in the
{{cassandra-test-report.txt}}, but since the parallelisation of dtests only
timings of splits are now listed. The timings will become accessible post
CASSANDRA-16128 (with the full test xml
[kept|https://github.com/apache/cassandra-builds/compare/master...thelastpickle:mck/jenkins--print-git-shas-and-website-build#diff-a76ac7fa36779199fe7e4fe917ac41bcR252]
on nightlies.a.o).
> 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
>
> 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]
