Startup time and used RAM scalability of PocoCapsule

18 views
Skip to first unread message

Philipp

unread,
Sep 2, 2010, 10:10:09 AM9/2/10
to pococapsule
Hi,

has somebody already evaluated the impact of using PocoCapsule
(instantiate components and wire them together) on application start
up time? I mean how the IOC overhead (CPU and RAM) per component
scales depending on app size (10->100->1000->10000 wired components)
compared with doing it in the traditional way (hardcoded).

Thanks,
Philipp

Ke Jin

unread,
Sep 2, 2010, 1:46:10 PM9/2/10
to pococapsule
wiring up 10,000 components sound like a mis-use of IoC container. IoC
containers are not designed for wiring up low level objects (such an
array to a hash table etc.), but for wiring/deploying applications
from service level components. It is rare a single application
executable contains up to 1,000 (not to mention more than 10,000)
service level components.

Ke

Philipp

unread,
Sep 3, 2010, 5:50:24 PM9/3/10
to pococapsule
Hi Ke,

I totally agree, 10 000 is an extreme case and usually an indication
for inappropriate modularization.

Nevertheless I'd consider such an evaluation as very helpful to be
aware of what the container is capable / has been designed to do and
within which limits it should be used in a real-world application.
Or putting it in other words I wouldn't want to make assumptions on
it's impact to app start up time or other runtime qualities based on a
simplistic prototype / hello world example.

So I'd really appreciate if somebody already conducted such tests and
would be willing to share the results or just the experience one made
in a project with regards to performance.

Thanks,
Philipp
BTW: I'd expect most apps to consist of some dozens up to few hundreds
of components.
Reply all
Reply to author
Forward
0 new messages