|Speeding up resolution and server start up [message #570259]
||Thu, 06 May 2010 14:47
| Dmitry Sklyut
Registered: January 2010
I think this issue will come up sooner than later and I would like to start a discussion early and maybe see if there are some ways to progressively adress it before initial Virgo release.
The issue I am talking about is related and very similar to this thread from dm-server forum: http://forum.springsource.org/showthread.php?t=86495&hig hlight=launcher.bundles
We are also noticing fairly significant start up time around 3 - 4 min (on OSX, windouz take longer as -clean takes much longer there) with final deployed bundle count around 190 (includes all third-party dependencies). The mix is fairly common in the enterprise apps. Hibernate/JPA (single session factory across all deployments), 3 webapps, some services bundles, datasource, activemq.
I strongly suspect that this situation is either because of the lag in service resolution between bundles or "side state" resolution. I will be trying to set-up all/most of common thirdparty deps in a plan and make sure that those are deployed early in user region start-up sequence to see if resolution happens faster.
I would also be happy to try and profile this process. I would like to start with a simple "StopWatch" type of a process that just tracks time that each individual bundle spends in ApplicationContext creation and try to correlate that with the over all start up scheme moving to a YourKit/JProfiler after that.
What would be the recommended areas of the system to look at in profiler? What should I be looking for outside of time spent and call count? Any pointers are welcomed as we are burning development time right now on start/update/restart cycle.
Powered by FUDForum
. Page generated in 0.01731 seconds