You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2021/08/08 10:18:00 UTC
[jira] [Resolved] (FELIX-6400) Reduce resource consumption during
component checks
[ https://issues.apache.org/jira/browse/FELIX-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved FELIX-6400.
-------------------------------------
Resolution: Fixed
Implemented in https://github.com/apache/felix-dev/commit/5f8217865be229eb915fd99f2be2a83b4b8868bd by using a simple cache that gets cleared whenever a change in the ds runtime happens
> Reduce resource consumption during component checks
> ---------------------------------------------------
>
> Key: FELIX-6400
> URL: https://issues.apache.org/jira/browse/FELIX-6400
> Project: Felix
> Issue Type: Improvement
> Components: Health Checks
> Affects Versions: healthcheck.generalchecks 2.0.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: healthcheck.generalchecks 2.0.8
>
>
> the components health check is each time (every 5 secs) iteration over all DS components just to check for a few. The iteration includes access to the service registry which (in Felix framework 6.x) has a lock
> There are two optimizations:
> - components check should only check for the configured ones instead of iterating over all components just to find the ones interested in
> - the resultcan be cached until an event occurs (service changed event of the SCR runtime as the runtime has a change count property to exactly avoid polling)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)