 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Performance / June 2006Application startup time
Hi, We're finishing our Windows Forms application, using .NET 2.0. Our application is really big, about 1,000,000 lines of code and some 400+ forms and user controls. Startup time is really slow, although we're not doing much at all, just showing the login screen. Also, during execution, the loading process of user controls can be slow. Basically, I wanted to know what can be done to improve application startup time and general performance. Thanks in advance for any help given. Regards, paulo One option is to run profiling tools to see what section of code is slowing it down. Other than that I am not aware of any other ways to pin point slow code. You could also ngen the assemblies, see if that makes a difference. > Hi, > [quoted text clipped - 9 lines] > Regards, > paulo There have been some good articles in various issues of MSDN magazine this year: http://msdn.microsoft.com/msdnmag/ We have a similar size application and the following helped us: 1. Reference as few assemblies as possible. This is tricky. I'm not saying not to use all the great tools in the .NET Framework, but reference as few distinct classes as possible in your start up code. For example, one reference to a class in System.Xml will require that the assembly be loaded. Assembly load time is very, very costly. My initial guess is this is what you are experiencing. 2. Make sure you are using release builds with optimized code. I know this seems obvious. 3. Use NGen to compile your assemblies to native instructions. This can eliminate the need to JIT. 4. Sign all your assemblies and put them in the GAC. If your assemblies are not in the GAC then all pages of the assembly must be loaded and validated before you can use the assembly. This is expensive! 5. Specify load addresses on your assemblies to avoid rebasing. This article helped me a lot: http://msdn.microsoft.com/msdnmag/issues/06/02/CLRInsideOut/default.aspx. I hope that helps. If it does help, and when you find time <grin>, I would appreciate it if you shared your performance metrics with me. I can be reached at bil_lo@c_u.net (remove all underscores). Best of luck! Bill O'Neill Enterprise Architect Computers Unlimited > Hi, > [quoted text clipped - 9 lines] > Regards, > paulo Bill, Thanks for including that link; we've beem grumbling about the startup time for one of our apps for some time now. Steve > This article helped me a lot: > http://msdn.microsoft.com/msdnmag/issues/06/02/CLRInsideOut/default.aspx. Hi Bill, I will try to implement your advice. If I figure out anything important beyond the information you provided, I will gladly contact you. Thanks for your help. Regards, paulo > There have been some good articles in various issues of MSDN magazine this > year: http://msdn.microsoft.com/msdnmag/ [quoted text clipped - 41 lines] >> Regards, >> paulo One hint. I recently when through the app startup optimization process. These tips are good. The one thing i'd skip is worrying about the base address of your dll's. Our product has about 30 dlls and I went through the fun of calculating unique base addresses for each dll so they dont get rebased at runtime. took about a day all said, and I didnt get an ounce of measurable startup time reduction. I dont think its worth the hastle of doing and maintaining > There have been some good articles in various issues of MSDN magazine this > year: http://msdn.microsoft.com/msdnmag/ [quoted text clipped - 41 lines] > > Regards, > > paulo I recently read an article or a blog (unfortunatly, I don't remember where, so I cannot provide a link) about application startup time. One of the options mentioned in the article was to split the application in multiple smaller assemblies. This would result in faster startup time, but also multiple smaller delays when other parts of the application are started, and their assemblies need to be loaded at that time. I haven't tried it (yet), but maybe it could help you. Also, although it does not speed up the startup, showing a splash screen during startup can improve the experience for the user that is waiting. Joris > Hi, > [quoted text clipped - 9 lines] > Regards, > paulo Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.