On 9/23/13 03:19 , Roland wrote:
Roland wrote
[...]It would be nice if the wires also can be cached persistently in some
way.
I'm no Felix-expert and do not know the exact implementation, but I'm
assuming that Felix creats a hash table of wire-objects to resolve
dependencies at runtime. Generating wires takes a lot of time. On the way to
work I had the spontaneous idea that we can implement a lookup table based
on the principals of the memory management. As the base address we could use
the bundle ID and for the offset we could use for instance the ASCII code of
the package name + version or any sum of digits. The advantage would be that
this kind of table can be dumped very simple in the bundle cache. We do not
need to generate Wire-objects at startup, this can be done concurrently
after startup or at the time when they are explicitly requested. I'm just
thinking out loud.
How do you feel about that?
I'm confused as to whether you are talking about resolved wirings or the
data structure in which capabilities are stored for resolving dependencies.
At one time during my GlassFish days I implemented a quick and dirty
mechanism to persist wires and I didn't notice any huge performance
advantage for a normal resolve. Granted, for a complex resolve it would
make a difference, but in the class of GlassFish with a couple hundred
bundles and no inconsistencies, it made little difference.
-> richard
Regards,
Roland
--
View this message in context:
http://apache-felix.18485.x6.nabble.com/How-to-improve-the-start-time-of-Apache-Felix-tp5004833p5005114.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
