Hi Minto I think currently TcManager takes care of registering the Triple Collections as services. For that it needs to be active by default.
I Think it would be good to have a separate service that takes care about registering the individual Triplecollection-Services (and which can be configured not to do anything, as this might be easier than disabling) and the TcManager to be activated only if a component actually requests it. Cheers, Reto On Wed, Aug 6, 2014 at 3:28 PM, Minto van der Sluis <[email protected]> wrote: > Hi, > > Just noticed that the TcManager responds to activation of > WeightedTcProviders. Unfortunately this slows down my application > startup dramatically when using the Virtuoso TcProvider. Let me explain > what happens: > > 1) Virtuoso TcProvider becomes active and the TcManager is notified > (bindWeightedTcProvider) > 2) TcManager (or better XXXX) requests a list of all provided graphs > 3) Each provided graph is retrieved > (TcProviderMultiplexer.weightedProviderAdded) > 3.1) cached in a map (for mgraphs) > 3.2) is made available as a service > 4) getting each graph involve some network roundtrips in the Virtuoso > provider > > In my development environment I already have approx 1500 graphs and this > process consumes a number of minutes. In production I have already about > 8,000 growing by 200+ a week. So for me this behaviour is not > acceptable. Especially since I do not use TcManager, but connect with > the TcProvider directly. > > So now I wonder how I can disable the TcManager. I can stop the bundle > but I'd rather have the bundle not start at all. Or at least disable > this behaviour. > > Any hints? > > Regards, > > Minto > >
