|
|
|
|
|
|
There has occurred a perf regression in eap-6x-Weld-perf-bean-testing-producers test case in EAP 6.4.1.CR2:
Jenkins job:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Performance-Weld/job/eap-6x-Weld-perf-bean-testing-producers/
Deployment times on EAP 6.4.0:
[build #156|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Performance-Weld/job/eap-6x-Weld-perf-bean-testing-producers/156/artifact/report/log.txt]; ran 1. April: 16.30 s
[build #159|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Performance-Weld/job/eap-6x-Weld-perf-bean-testing-producers/159/artifact/report/log.txt]; ran 19. May: 15.51 s
Deployment times on EAP 6.4.1:
[build #157|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Performance-Weld/job/eap-6x-Weld-perf-bean-testing-producers/157/artifact/report/log.txt]; ran 14. May: 18.37 s
[build #158|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Performance-Weld/job/eap-6x-Weld-perf-bean-testing-producers/158/artifact/report/log.txt]; ran 19. May: 19.22 s
As you can see there is a significant difference between two runs in the same day.
In EAP 6.4.1.CR2 is an Weld update 1.1.28.Final-redhat-1 -> 1.1.29.Final-redhat-1 ([comparison|https://github.com/weld/core/compare/1.1.28.Final...1.1.29.Final])
This is the only one eap-6x-Weld-perf-bean-testing-* job that exhibits such a differences
|
|
|
|
|
|
