felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre De Rop <pierre.de...@gmail.com>
Subject Re: [jira] [Commented] (FELIX-5469) Methodcache system size property is not used
Date Thu, 29 Dec 2016 11:36:25 GMT
ok, thanks, will change the issue to resolved.

So, I see that you are in a point where you are doing some performance
tests for your application. I wonder if you are using the concurrent mode
of dependency manager ?
Mixing DM filter indices + DM concurrent mode may significantly reduce
startup time, especially if you have thousands of components which have
some time consuming start methods.

DM concurrent mode has a kind of actor model: each component remains
"single threaded" (all osgi events are handled serially), but multiple
distinct components can be started concurrently. In case you are
interested, don't hesitate to ask on the users mailing list, I will provide
support. you can check [1] for general description about DM concurrent
mode, and [2] for a concrete example (in the example, I'm using a pattern
which allows to specify whether or not a given component can be started in
a given thread pool, or if it must be handled synchronously, as it is the
case by default, but you can also have a model where all components are by
default started concurrently).

[1]
http://felix.staging.apache.org/documentation/subprojects/apache-felix-dependency-manager/reference/thread-model.html
[2]
http://svn.apache.org/viewvc/felix/trunk/dependencymanager/org.apache.felix.dependencymanager.samples/src/org/apache/felix/dependencymanager/samples/tpool/

hope this helps;
/Pierre

On Thu, Dec 29, 2016 at 12:13 PM, Jeroen Daanen (JIRA) <jira@apache.org>
wrote:

>
>     [ https://issues.apache.org/jira/browse/FELIX-5469?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=15785123#comment-15785123 ]
>
> Jeroen Daanen commented on FELIX-5469:
> --------------------------------------
>
> Yes this is ok for me, the issue can be closed. Thanks!
>
> Here we use a cache size of 10000. Indeed the caching improves the
> performance noticeably. I also checked if the method cache gets actually
> full and in our case it gets full sometimes when loading a large
> configuration, even with a cache size of 10000 (the number of services
> depends on what an end-user has configured).
> What the best default value for every use of the dependency manager would
> be is a difficult question of course, I think 4096 is a good value and if
> someone needs more, they can just specify the VM argument.
>
>
> > Methodcache system size property is not used
> > --------------------------------------------
> >
> >                 Key: FELIX-5469
> >                 URL: https://issues.apache.org/jira/browse/FELIX-5469
> >             Project: Felix
> >          Issue Type: Bug
> >          Components: Dependency Manager
> >    Affects Versions: org.apache.felix.dependencymanager-r1
> >            Reporter: Jeroen Daanen
> >            Assignee: Pierre De Rop
> >            Priority: Trivial
> >             Fix For: org.apache.felix.dependencymanager-r9
> >
> >
> > The code in InvocationUtil to set a custom size for the method cache has
> been commented out. See InvocationUtil.java.
> > The default is not large enough for me.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message