Re: [release] [OpenDaylight][TSC] Fluorine SR3 status - candidate sign off


Robert Varga
 

On 30/05/2019 20:58, Luis Gomez wrote:

2) Some perf regression in controller:

https://jenkins.opendaylight.org/releng/job/controller-csit-3node-clustering-ask-all-neon/247/robot/controller-clustering-ask.txt/Chasing%20The%20Leader/Unregister_Candidates_And_Validate_Criteria/
<https://jenkins.opendaylight.org/releng/job/controller-csit-3node-clustering-ask-all-neon/247/robot/controller-clustering-ask.txt/Chasing
The Leader/Unregister_Candidates_And_Validate_Criteria/>
#2‚Äč44
27-May-2019 09:46

Hmm... what is the usual achieved rate?

Jam0, we've been messing with those numbers last, but I do not remember
the specifics...

https://jenkins.opendaylight.org/releng/job/controller-csit-3node-clustering-tell-all-fluorine/220/robot/controller-clustering-tell.txt/Chasing%20The%20Leader/Unregister_Candidates_And_Validate_Criteria/
<https://jenkins.opendaylight.org/releng/job/controller-csit-3node-clustering-tell-all-fluorine/220/robot/controller-clustering-tell.txt/Chasing
The Leader/Unregister_Candidates_And_Validate_Criteria/>

I am not sure how critical is this perf test.
Well, regressions needs to be investigated. On the other hand, we have
seen problems with Nexus, so this could (I am not saying it is) an env
issue.

Let's see what the usual rates were, but I think these should actually
improve in this release :)

Also, let's make this a blocker until we understand more. It is the last
SR after all...

Regards,
Robert

Join integration-dev@lists.opendaylight.org to automatically receive all group messages.