ppalaga commented on issue #1672: URL: https://github.com/apache/camel-quarkus/issues/1672#issuecomment-687050209
> * Highlighted log line shows that it took 25 mins to finish as2 integration test > > > [INFO] Camel Quarkus :: Integration Tests :: AS2 .......... SUCCESS [25:41 min] > > On my local computer it takes usually about 5-6 mins or similar. So I'm not sure what could be wrong. Yeah, it's fast on my computer too. There are two factors to take into account: * GH Actions nodes have just two cores which are probably slower than what we have on our desk/laptops. * Native compilation gets much slower with limited RAM. Have you activated the `ci` profile that sets `<quarkus.native.native-image-xmx>6g</quarkus.native.native-image-xmx>` https://github.com/apache/camel-quarkus/blob/master/integration-tests/as2/pom.xml#L146 ? The 25mins on the CI are real and too much at the same time. We should try to do something about that. Limiting the bouncy castle algos sounds like a good idea, and I'd be interested in seeing numbers in the CI. BTW, we have `camel-quarkus-support-bouncycastle` extension, so I think the code should go there and the new config options should be namespaced under ` quarkus.camel.bouncycastle.*` If reducing bouncy castle algos is going to help here, we may try experimenting with it in other tests too where BC is included. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
