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

Michael Semb Wever edited comment on CASSANDRA-16079 at 12/4/20, 10:21 AM:
---------------------------------------------------------------------------

Now that CASSANDRA-16205 is merged…

For just the work in this ticket, here's a run: 
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/248/pipeline
This builds on the following patches:
- ccm 
[mck/16205|https://github.com/riptano/ccm/compare/cassandra-test...thelastpickle:mck/16205]
- cassandra-dtest 
[mck/16079|https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:mck/16079]

And, for work in this ticket in combination with CASSANDRA-13701, here's a run: 
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/246/pipeline
This builds on the following patches:
- cassandra 
[mck/trunk_13701|https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_13701]
- ccm 
[mck/16205|https://github.com/riptano/ccm/compare/cassandra-test...thelastpickle:mck/16205]
- cassandra-dtest 
[mck/16079|https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:mck/16079]

Both these runs have the same performance, so any degradation is no longer 
attributable to the 13701. 

It's not yet clear what the performance degradation or improvement from this 
ticket's patches are. Looking at 
https://ci-cassandra.apache.org/job/Cassandra-trunk-dtest/buildTimeTrend it 
suggests that the ccm and dtest patches for this ticket could be improving 
dtest performance by ~20% (without looking at jenkins agents involved or system 
saturation at the time of each run).


was (Author: michaelsembwever):
Now that CASSANDRA-16205 is merged…

For just the work in this ticket, here's a run: 
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/248/pipeline
This builds on the following patches:
- ccm 
[mck/16205|https://github.com/riptano/ccm/compare/cassandra-test...thelastpickle:mck/16205]
- cassandra-dtest 
[mck/16079|https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:mck/16079]

And, for work in this ticket in combination with CASSANDRA-13701, here's a run: 
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/246/pipeline
This builds on the following patches:
- cassandra 
[mck/trunk_13701|https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_13701]
- ccm 
[mck/16205|https://github.com/riptano/ccm/compare/cassandra-test...thelastpickle:mck/16205]
- cassandra-dtest 
[mck/16079|https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:mck/16079]

Both these runs have the same performance, so any degradation is no longer 
attributable to the 13701. It's not yet clear what the performance degradation 
from this ticket's patches are.


> 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