JiriOndrusek commented on issue #1672: URL: https://github.com/apache/camel-quarkus/issues/1672#issuecomment-687004283
Hi @ppalaga, I've looked into this problem and I see 2 items: - 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. - From my local RAM consumption it seems, that about a half of the consumption is caused by presence of bouncy castle (extension support-bouncycastle). Here are some measurements: #### Local execution with **current code**: >[camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner:14157] classlist: 9,643.39 ms, 1.68 GB ... [camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner:14157] [total]: 304,349.07 ms, 12.07 GB [INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildStep] Execute [objcopy, --strip-debug, /home/jondruse/git/camel-quarkus/integration-tests/as2/target/camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner] [INFO] [io.quarkus.deployment.QuarkusAugmentor] Quarkus augmentation completed in **308998ms** ... [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: **05:34 min** #### Local execution **without bouncycastle**: >[camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner:16243] classlist: 8,989.76 ms, 1.17 GB ... [camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner:16243] [total]: 154,163.27 ms, 5.72 GB [INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildStep] Execute [objcopy, --strip-debug, /home/jondruse/git/camel-quarkus/integration-tests/as2/target/camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner] [INFO] [io.quarkus.deployment.QuarkusAugmentor] Quarkus augmentation completed in **157363ms** ... INFO] **_BUILD FAILURE_** [INFO] ------------------------------------------------------------------------ [INFO] Total time: **03:00 min** --- --- I've tried one optimization by registering only those algorithms/signatures, which are really used. WIP can be seen here https://github.com/apache/camel-quarkus/pull/1686, but CI job failed with unrelated issue. It would be nice to compare results from this test with the reported results. #### Local execution with optimization: >[camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner:13100] classlist: 9,949.54 ms, 0.93 GB ... [camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner:13100] [total]: 278,546.97 ms, 10.07 GB [INFO] [io.quarkus.deployment.pkg.steps.NativeImageBuildStep] Execute [objcopy, --strip-debug, /home/jondruse/git/camel-quarkus/integration-tests/as2/target/camel-quarkus-integration-test-as2-1.1.0-SNAPSHOT-runner] [INFO] [io.quarkus.deployment.QuarkusAugmentor] Quarkus augmentation completed in **284173ms** ... [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: **05:11 min** I can see an improvement (but not so big), what do you think? I think that it could be possible to add some as2 quarkus properties to define really needed bouncycastle services. In case of the current integration test it would look like: > quarkus.as2.digest=sha1,md5,sha512 quarkus.as2.asymmetric=rsa,x509 ---------------------------------------------------------------- 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]
