Dear,

We recently switched to Aries subsystems for the deployment of our
applications and we noticed a slow startup speed. We profiled the startup
and noticed that a lot of time was spent directly reading the bundles from
the zip files in the temp folder created by Aries
(inputStreamExtract******.zip).

We tried to change the Aries implementation to unpack the zip artifact into
the temporary folder so it is unpacked only once. Subsequent reads for the
bundles (jars) can be read directly from the folder. This delivered a 44%
increase in the total startup time of our application (277 bundles). The
install phase in this startup improved by 74%.

The change we did can be found at
https://github.com/apache/aries/compare/subsystem-2.0.x...WouterBanckenACA:io_performance_optimalisation?expand=1

As you can see we switched out the aries-utils FileSystem implementation
for our own implementation with the same API. Our filesystem implementation
simply unpacks the zip into a folder instead of copying it.

Are there any objections to this change? Can this be included in Aries in
some way?

Best regards,
Wouter Bancken

Reply via email to