Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Mon, 21 Aug 2017 14:12:00 +0000 (UTC)
From: "Vinay Shankar (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.13095636.1503063405000.79327.1503324720190@Atlassian.JIRA>
In-Reply-To: <JIRA.13095636.1503063405000@Atlassian.JIRA>
References: <JIRA.13095636.1503063405000@Atlassian.JIRA> <JIRA.13095636.1503063405212@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (KARAF-5314) The performance of profile builder
 used by karaf maven plugin has reduced significantly in 4.1 compared to 4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 21 Aug 2017 14:12:06 -0000


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

Vinay Shankar resolved KARAF-5314.
----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.1.3)
                   4.2.0

Fix available in the 4.2.0-SNAPSHOT master branch

> The performance of profile builder used by karaf maven plugin has reduced significantly in 4.1 compared to 4.0
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-5314
>                 URL: https://issues.apache.org/jira/browse/KARAF-5314
>             Project: Karaf
>          Issue Type: Bug
>            Reporter: Vinay Shankar
>             Fix For: 4.2.0
>
>
> The performance of profile builder used by karaf maven plugin has reduced significantly in 4.1 compared to 4.0. 
> The java streams API is being used in 4.1 to filter our the required features from the set of all features present in the repositories that are part of the profile. This is done in the "addFeatures" method in the "Builder.java" class in the "org.apache.karaf.profile.core" bundle. This change (from 4.0) has drastically reduced the performance. For a profile with ~900 features in all the repositories in the profile and ~300 required features from a highly complex feature dependency tree, this function is taking around 13min to complete. The same execution took around 3-5min in 4.0 (where simple for loops were being used). 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)