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

Aurélien Pupier edited comment on CAMEL-25880 at 10/22/26, 6:47 AM:
--------------------------------------------------------------------

camel-cxf-soap is still taking 5'13", a potential next bottleneck which could 
be improved as a lot of CPUs are available 
https://develocity.apache.org/s/vsg2b7mvsxp6q/timeline?details=d6ugykcrodphc&page=58

 !screenshot-2.png! 

and cxf soap spring is awaiting for it to start


was (Author: apupier):
camel-cxf-soap is still taking 5'13", a potential next bottleneck which could 
be improved as a lot of CPUs are available 
https://develocity.apache.org/s/vsg2b7mvsxp6q/timeline?details=d6ugykcrodphc&page=58

 !screenshot-2.png! 

> Improve test time of camel-cxf-spring-soap
> ------------------------------------------
>
>                 Key: CAMEL-25880
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25880
>             Project: Camel
>          Issue Type: Test
>          Components: camel-cxf
>    Affects Versions: 4.24.0
>            Reporter: Aurélien Pupier
>            Assignee: Aurélien Pupier
>            Priority: Major
>             Fix For: 4.24.0
>
>         Attachments: screenshot-1.png, screenshot-2.png
>
>
> This is an important bottleneck of build (well after the -T1C will be merged).
> In worst case, it is [running alone for 
> 6'|https://develocity.apache.org/s/qaf4axq6qn5ss/timeline?details=timogjvgguiuw&page=63]
>  on a 32' test build (43' ended to end Jenkins job). 
> Potential improvements:
> * the surefire test could be activated to launch in // Be extra cautious to 
> stay stable (port conflict, resource shared)
> * investigate why most of them are taking more than 1.5seconds, maybe some 
> initialization could be improved
> Note that camel-cxf-soap is taking 5' and seems that the 
> camel-cxf-spring-soap is waiting for it to be finished to start, so maybe 
> interesting to look at both at the same time. (or not and in this case, 
> create another issue)



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to