aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <>
Subject [jira] [Resolved] (ARIES-1357) BasicSubsystem can be used by the subsystem install process a factor 6 times faster
Date Thu, 24 Sep 2015 00:26:04 GMT


John Ross resolved ARIES-1357.
    Resolution: Fixed

This bug is being used for many things and becoming unwieldy.

1) The current preferred provider implementation which does not compare correctly anymore
(addressed in ARIES-1416)
2) The subsystem resource installer which should first install shared resources before the
child subsystems (addressed in ARIES-1416)
3) Optional dependencies ending up in a resource of synthesized type that is persisted in
the deployment manifest eventually causing problems on restart (addressed in ARIES-1404)

Attempts were made to address performance issues in the following:

ARIES-1388: Compute requirement filters only once.
ARIES-1356: getInstance method on the core Activator shows up on jvisualvm sampling during
performance analysis
ARIES-1359: Performance improvement on the findProviders method in the SystemRepository class
ARIES-1389: Compute service requirements and capabilities once in BundleRevisionResource.
ARIES-1390: BasicCapability should take advantage of the effective immutability of capabilities.
ARIES-1392: Provide a more efficient implementation of a system repository.
ARIES-1394: Provide more efficient implementations of the local and content repositories.
ARIES-1396: Use capability set when calculating subsystem dependencies.
ARIES-1397: Use capability set with preferred provider repository.

If anything remains or crops up anew, please open new bugs.

> BasicSubsystem can be used by the subsystem install process a factor 6 times faster
> -----------------------------------------------------------------------------------
>                 Key: ARIES-1357
>                 URL:
>             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
>         Attachments: 1701058.output, FelixResourceAdapter.patch,,
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, test-cases-1.patch
> 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

This message was sent by Atlassian JIRA

View raw message