| Embedded system startup time [message #875576] |
Tue, 22 May 2012 21:23  |
Eclipse User |
|
|
|
I am involved with building an embedded system using Virgo Tomcat. Our basic OS (on an Atom processor, running Linux) boots very quickly, but it takes several minutes for our application to start up.
The app is based on Virgo Tomcat, and I am looking for guidance as to how we can optimize startup.
For instance, it seems that the 'work' directory is rebuilt from the ground up on a reboot. Is there any way to preserve the contents - a sort of 'suspend' mode, or is this behavior inherent in the way Virgo Tomcat works?
Also, is there a way to determine which artifacts are, or will be needed? Any way to prune out or defer some artifacts, or is that list already optimized by Virgo Tomcat?
I'm looking for a factor of 5 improvement, and I don't know if it is reasonable to shoot for that, or if we are attempting to misuse a 'big iron' software stack on a low-horsepower embedded system.
Opinions, suggestions, etc. are all welcome.
[Updated on: Tue, 22 May 2012 21:24] by Moderator |
|
|
|
|
|
|
| Re: Embedded system startup time [message #879145 is a reply to message #875576] |
Wed, 30 May 2012 11:47  |
| Eclipse User |
|
|
|
Is there a way we can have our cake and eat it too?
Or, put another way, is there any way to configure or optimize Virgo's startup experience other than to go with the more stripped down distributions?
I'm wondering, as was the poster, if there's a way to snapshot all of the bundle resolutions so that Virgo does not have to recalculate all of the dependencies and resolution in the repositories. Or... if there are common practices we can adopt in defining a bundle and its dependencies that help Virgo do the work faster.
|
|
|
Powered by
FUDForum. Page generated in 0.07358 seconds
Home