On 4/13/11 5:03, Holger Hoffstätte wrote:
On 13.04.2011 05:49, David Erickson wrote:
I'm working on an application where performance is critical, but we'd
like to take advantage of the dynamism inherent in OSGi to allow in
place updates and feature additions. I've played with Spring DM and
Blueprint (both Gemini and Aries), and both seem to have significant
overheads when making function calls using their service proxies. I
That's a shortcoming of these component models and not something
inherent to service interactions aross OSGi bundles. "Regular" services
are plain objects and method calls, and as fast as they can be.
I don't know the state of Aries' internals, but with the upcoming
release of the OSGi weaving service a Blueprint implementation could use
generated bytecode proxies, which are typically at least>10x faster
again. Or maybe they already do and the call sites are just too
big/megamorphic for HotSpot.
iPOJO uses byte code generated proxies or you can disable proxies and
just have direct service object references injected. Otherwise, as Felix
says, DS is a lightweight, albeit less feature rich, solution.
-> richard
-h
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
