You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Tom Watson (Jira)" <ji...@apache.org> on 2020/11/30 14:50:00 UTC

[jira] [Updated] (FELIX-6155) Add caching of service component metadata

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

Tom Watson updated FELIX-6155:
------------------------------
    Fix Version/s: scr-2.1.18

> Add caching of service component metadata
> -----------------------------------------
>
>                 Key: FELIX-6155
>                 URL: https://issues.apache.org/jira/browse/FELIX-6155
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-2.1.16
>            Reporter: Tom Watson
>            Assignee: Tom Watson
>            Priority: Major
>             Fix For: scr-2.1.18
>
>
> SCR has to discover and parse the component XML files of all bundles that have the Service-Component header.  In a configuration that has a significant number of bundles using SCR this overhead begins to add up.  For modest number of bundles (~300) I see this taking nearly 200 ms in an overall application launch time of 3000 ms.
> This overhead can be greatly reduced if we cached the component metadata such that on restart the XML files do not need to be discovered or parsed, or even having to look for the Service-Component header in all active bundles.  I am working on a caching implementation that I would like to contribute which I plan to have disabled by default so we can experiment with enabling such a cache for cases where a relaunch performance time is critical.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)