[ 
https://issues.apache.org/jira/browse/ARIES-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bas updated ARIES-1357:
-----------------------
    Attachment: PreferredProviderIsEqual.patch

The preferred provider repository should be able to compare resources 
originating from different locations. For example one from an obr repository 
and one that is already installed. So using the ResourceHelper.areEqual is 
required here.
Using this patch I was able to install our subsystems while using revision 
1701286 of 2.0.3-SNAPSHOT. 

> 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, 
> 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)

Reply via email to