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

Posted to dev@felix.apache.org by "Pierre De Rop (JIRA)" <ji...@apache.org> on 2017/06/27 07:09:00 UTC

[jira] [Updated] (FELIX-5623) Improve performance of ComponentImpl.getName method

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

Pierre De Rop updated FELIX-5623:
---------------------------------
    Fix Version/s:     (was: org.apache.felix.dependencymanager-r10)
                   org.apache.felix.dependencymanager-r11

> Improve performance of ComponentImpl.getName method
> ---------------------------------------------------
>
>                 Key: FELIX-5623
>                 URL: https://issues.apache.org/jira/browse/FELIX-5623
>             Project: Felix
>          Issue Type: Improvement
>          Components: Dependency Manager
>            Reporter: Raluca Grigoras
>            Assignee: Pierre De Rop
>            Priority: Minor
>             Fix For: org.apache.felix.dependencymanager-r11
>
>         Attachments: FELIX-5632.patch
>
>
> We are using the dependency manager diagnostics API (the dependency graph) in our application to display all components (registered and unregistered) in the application UI (similar to the 'dm' shell command). We ran into a performance problem (requesting the whole dependency graph takes very long), and after profiling I found out that the ComponentImpl.getName method is the reason. The component name is generated each time the method is called, making the dependency graph generation slow.



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