[
https://issues.apache.org/jira/browse/ARIES-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740793#comment-14740793
]
Bas commented on ARIES-1357:
----------------------------
Hi,
I wanted to post some preliminary results because they might be of use.
When we update to the snapshot 2.0.3-SNAPSHOT rev 1700842 we can install our
subsystems and everything except the Subsystem-ImportService seems to work ok.
Because of this services problem we can't start our subsystems so no
performance numbers yet. In a comment above you asked about our
Subsystem-ImportServices header, do you know more about this issue?
When we go to revision 1701058 our subsystems do not install anymore. The
problems that appear in the log and console I attached to this issue.
When we go to revision 1701121 the subsystems can't be installed anymore,
instead the resolver is continuously busy and doesn't stop anymore. When
debugging it seems is has a lot of uses conflicts. We use a preferred provider
header to give the resolver some boundaries (so it can handle updates of our
components) but it almost looks like the resolver doesn't use it anymore.
I'm gonna try and get the importservice header going again to find out some
more.
> 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: ManyFeaturesWithSharedBundlesTest.java,
> 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)
