key question is about the scalability of the runtime, in terms of
of services, 100K, 1M, 10M, etc
and unregistering them, churn over long period of time
it primarily memory bound? Assuming that services are not CPU heavy or
details of the experiment we had:
code is pretty straightforward. We only have a 5 Service Classes. We
add an ID property to each service object we register and later look it
up using that ID.
The look up through getServiceReferences() took
4-5 seconds when we have 200K services registered.
shed some light for the
Do you think lazy service creation may be the reason? Is lazy
creation the default? How to configure it?
- Can you outline the steps to
to build index? Do you mean trapping the
registration events and build the needed indexes?
Registration: we register all the 200K service instances in a loop.
They are one of 5 different server classes.
props = new Hashtable<String, String>(1);
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of BJ Hargrave
Friday, May 04, 2012 10:19 AM
To: Equinox development mailing
Subject: Re: [equinox-dev] Service Lookup by GUID very
also indexes by objectClass alone. So I am not sure what the
discrepancy is here. Would be nice to have the test case code to
analyze. Stanley, can you post a gist with the code?
S. Hall" <heavy@xxxxxxxxxxxxxx>
development mailing list <equinox-dev@xxxxxxxxxxx>,
[equinox-dev] Service Lookup by GUID very Slow