You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/09/13 12:22:37 UTC

[jira] Closed: (FELIX-2552) Add caching PersistenceManager proxy

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

Felix Meschberger closed FELIX-2552.
------------------------------------


Closing issues after Configuration Admin 1.2.8 release

> Add caching PersistenceManager proxy
> ------------------------------------
>
>                 Key: FELIX-2552
>                 URL: https://issues.apache.org/jira/browse/FELIX-2552
>             Project: Felix
>          Issue Type: Improvement
>          Components: Configuration Admin
>    Affects Versions:  configadmin-1.2.4
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For:  configadmin-1.2.8
>
>
> Each call to the ConfigurationAdmin.listConfigurations method causes a call to the PersistenceManager.getDictionaries() method. The current file-based implementation of this interface scans the configuration location and loads configuration files each time this method is called. Depending on the number of stored configurations, this may sum up to a considerable amount of time,
> In an inhouse implementation using Declarative Services (Apache Felix SCR 1.6.0) and Configuration Admin the use of ConfigurationAdmin.listConfigurations by the Declarative Services implementation increases system startup time considerably. With a simple caching layer ontop of the file-based PersistenceManager service we were able to cut down ca. 10s of a total system startup time of roughly 25s.

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