You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2010/02/03 20:41:27 UTC

[jira] Created: (FELIX-2037) Improve resolver performance by making solution space searching smarter

Improve resolver performance by making solution space searching smarter
-----------------------------------------------------------------------

                 Key: FELIX-2037
                 URL: https://issues.apache.org/jira/browse/FELIX-2037
             Project: Felix
          Issue Type: Sub-task
          Components: Framework
    Affects Versions: felix-2.0.3
            Reporter: Richard S. Hall
            Assignee: Richard S. Hall
             Fix For: felix-3.0.0


The main performance issue with the current resolver algorithm is when a conflict is detected, it largely just blindly permutates to the next available possibility without trying to determine which possibility makes more sense. We need to make this smarter without losing the ability to check all/most viable solutions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (FELIX-2037) Improve resolver performance by making solution space searching smarter

Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.

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

Richard S. Hall closed FELIX-2037.
----------------------------------

    Resolution: Fixed

Closing this in preparation for the 3.0. Any future resolver issues should be opened as new JIRA issues.

> Improve resolver performance by making solution space searching smarter
> -----------------------------------------------------------------------
>
>                 Key: FELIX-2037
>                 URL: https://issues.apache.org/jira/browse/FELIX-2037
>             Project: Felix
>          Issue Type: Sub-task
>          Components: Framework
>    Affects Versions: framework-2.0.3
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: framework-3.0.0
>
>
> The main performance issue with the current resolver algorithm is when a conflict is detected, it largely just blindly permutates to the next available possibility without trying to determine which possibility makes more sense. We need to make this smarter without losing the ability to check all/most viable solutions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.