[
https://issues.apache.org/jira/browse/ARIES-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804376#comment-14804376
]
John Ross edited comment on ARIES-1357 at 9/18/15 12:45 AM:
------------------------------------------------------------
I was asking about the Subsystem-ImportService header because you're using it
on an application. Applications have this header, along with a number of
others, computed for them. They may not be overridden. You must use a composite
for that. Although the supplied header is being ignored, the computed header
might be equivalent.
I assume you are referring to attachment 1701058.output? If so, I'm not sure
what's responsible for generating it. Also, I'm having trouble relating it to
your comment because you said that the subsystems do not install. However, the
output appears to be talking about bundles that can't be started, which would
not happen during the installation phase. For example "-> Problem while
starting bundle [ 3][org.osgi.framework.BundleException:".
Keep in mind that there are two resolutions that occur. One is an offline
resolution that occurs at installation time in order to identify and gather
dependencies and to ensure that all required dependencies are present. This
resolution is performed by the subsystems implementation. The second resolution
occurs at start time and is done by the framework, although the subsystems
implementation is responsible for ensuring the sharing policies are correct.
was (Author: [email protected]):
I was asking about the Subsystem-ImportService header because you're using it
on an application. Applications have this header, along with a number of
others, computed for them. They may not be overridden. You must use a composite
for that. Although the supplied header is being ignored, the computed header
might be equivalent.
I assume you are referring to attachment 1701058.output? If so, I'm not sure
what's responsible for generating it. Also, I'm having trouble relating it to
your comment because you said that the subsystems do not install. However, the
output appears to be talking about bundles that can't be started, which would
not happen during the installation phase. For example "-> Problem while
starting bundle [ 3][org.osgi.framework.BundleException:".
Keep in mind that there are two resolutions that occur. One is an offline
resolution that occurs at installation time in order to identify and gather
dependencies and to ensure that all required dependencies are present. This
resolution is performed by the subsystems implementation. The second resolution
occurs at start time and is done by the framework, although the subsystems
implementation is responsible for providing the resolve context and ensuring
the sharing policies are correct.
> BasicSubsystem can be used by the subsystem install process a factor 6 times
> faster
> -----------------------------------------------------------------------------------
>
> Key: ARIES-1357
> URL: https://issues.apache.org/jira/browse/ARIES-1357
> Project: Aries
> Issue Type: Improvement
> Components: Subsystem
> Affects Versions: subsystem-core-1.2.0, subsystem-2.0.1
> Environment: linux windows java
> Reporter: Bas
> Assignee: John Ross
> Labels: patch, performance
> Fix For: subsystem-core-1.2.0, subsystem-2.0.1
>
> Attachments: 1701058.output, FelixResourceAdapter.patch,
> ManyFeaturesWithSharedBundlesTest.java, PreferredProviderIsEqual.patch,
> SubsystemResourceInstallerInstallOrder.patch,
> nl.capesystemsintegration.emagiz.flow.emagiz.mikrotik.process_1.1.0.esa,
> patch-all-performance-fixes.patch, patch-basicsubsystem.patch,
> performance-105-afterrestart.nps, subsystem-basicsubsystem-patch.txt
>
>
> The problem was poor performance while installing a subsystem on a container
> with 200+ subsystems installed.
> While doing performance analyses on the subsystem install process we noticed
> the BasicSubsystem is working a lot with its manifest instead of
> pre-calculating data that is used a lot.
> While using the pre-patch version of BasicSubsystem a subsystem install
> (while having 200+ running subsystems) could take more than a minute. While
> using the patched version where we pre-calculate highly used data when a new
> subsystem manifest or deployment manifest is set we could bring it down to 10
> seconds. We only pre-calculated the data that was highly used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
