Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Date: Fri, 17 Apr 2015 20:26:59 +0000 (UTC)
From: "Thomas Watson (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Message-ID: <JIRA.12744476.1411825327000.34712.1429302419120@Atlassian.JIRA>
In-Reply-To: <JIRA.12744476.1411825327000@Atlassian.JIRA>
References: <JIRA.12744476.1411825327000@Atlassian.JIRA>
 <JIRA.12744476.1411825327796@arcas>
Subject: [jira] [Commented] (FELIX-4656) Improve memory usage and speed of
 the resolver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500601#comment-14500601 ] 

Thomas Watson commented on FELIX-4656:
--------------------------------------

I agree that a release should be done with the current code.  Other issues I raised should be done in another jira.  I suggest waiting until we have proof of another performance issue or proof that valid solutions are being discarded without being processed.

> Improve memory usage and speed of the resolver
> ----------------------------------------------
>
>                 Key: FELIX-4656
>                 URL: https://issues.apache.org/jira/browse/FELIX-4656
>             Project: Felix
>          Issue Type: Improvement
>          Components: Resolver
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: resolver-1.2.0
>
>         Attachments: FELIX-4656.patch
>
>
> During big resolutions (> 100 bundles), the memory consumption can become very huge, mostly by keeping a lot of copies of the Candidates object.
> I want to lower the memory requirements of the resolver without touching the algorithm at all (which would be a different improvement).
> This can be done by using :
>   * lower memory intensive collections
>   * do smart copies of those collections (where they would only actually copy the data when modify)
> The second item is slightly more difficult to achieve, as the maps in the Candidate objects contains Set and List, which would mean that those must be copied too.  So it could actually be complementary, if achievable.
> For the first one, the HashMap and HashSet are very memory intensive.  I'll introduce two new collections which will lower the requirements.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)