| Groups | Blog | Home |
dotnet performance : How to shorten startup time on low power machine?
Unfortunately this application needs about 23 seconds to startup, which isn't acceptable. The app uses a custom library which in turn uses DirectX9 managed extensions. This library (assembly) contains about 10 assembly references. So I used 'ngen' to create native images of these assemblies. However this doesn't help. Are there other ways to improve the startup time? How can I accelerate loading assemblies? Can I disable some security checks for instance? (I use the default machine configuration so far) Is there a way to keep assemblies loaded? Any tips, hints, and tricks are welcome. Thanks, Claus
96 megs isn't a whole lot. Are you running into any memory thrashing?
Check Task Manager to see if you are using more memory than is physically available in the machine. If so, upgrade to 128MB. It sounds like you have done most everything you can do to speed up .NET. But you are using not only DirectX managed extensions, but also DirectX underneath, plus probably a bunch of other libraries. Does it run as slowly on a 366MHz machine with 256MB of RAM? That would be a clue right there. Have you tried it with different operating systems? Windows 98 is going to have a much smaller footprint than Windows Server 2003... [quoted text, click to view] "news.microsoft.com" <klammer@utanet.at> wrote in message news:uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl... > I've to run .net applications on a low power machine (366mhz and 96mb ram!). > Unfortunately this application needs about 23 seconds to startup, which > isn't acceptable. The app uses a custom library which in turn uses DirectX9 > managed extensions. > This library (assembly) contains about 10 assembly references. So I used > 'ngen' to create native images of these assemblies. However this doesn't > help. > > Are there other ways to improve the startup time? > How can I accelerate loading assemblies? Can I disable some security checks > for instance? (I use the default machine configuration so far) > Is there a way to keep assemblies loaded? > > Any tips, hints, and tricks are welcome. > > Thanks, Claus > >
Hi there. From what I've read about .NET in general, a few concepts of the framework relies on computer hardware becoming faster and hard drives becoming bigger. So, for example, the idea of running assemblies side-by-side is now more acceptable as these days RAM is cheaper. So Microsoft didn't worry too much about making .NET optimised to run on older computer's. Running a .NET app on a 366MHz computer is a no win situation I feel. Such has been mentioned I would certainly recommend increasing the RAM to at least 256MB, providing that the type of RAM you need is still available. I wouldn't waste too much of your time on this.
Have you tried profiling your application? Things are not always what they appear, and you never know what is actually happening at startup time until you measure it. Beyond that, my tips would be: 1) Make sure you ngen all the assemblies that are used at startup (including the application). If you see mscorjit.dll loaded into your process, it means that you missed something (or that the application is generating code dynamically which is an even bigger perf problem). 2) After you profile your application, see if you can avoid loading some of the assemblies (by deferring initialization until later, or maybe not using them at all). Avoiding assembly loads can give you big wins. Good luck! -- Ori. -------------------- [quoted text, click to view] >From: "Jason Smith" <jason@nospam.com> >References: <uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl> >Subject: Re: How to shorten startup time on low power machine? >Date: Fri, 24 Oct 2003 21:29:02 -0600 >Lines: 39 >X-Priority: 3 >X-MSMail-Priority: Normal >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 >Message-ID: <udIflgqmDHA.684@TK2MSFTNGP09.phx.gbl> >Newsgroups: microsoft.public.dotnet.framework.performance >NNTP-Posting-Host: dpc6682114093.direcpc.com 66.82.114.93 >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl >Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.performance:5692 >X-Tomcat-NG: microsoft.public.dotnet.framework.performance > >96 megs isn't a whole lot. Are you running into any memory thrashing? >Check Task Manager to see if you are using more memory than is physically >available in the machine. If so, upgrade to 128MB. > >It sounds like you have done most everything you can do to speed up .NET. >But you are using not only DirectX managed extensions, but also DirectX >underneath, plus probably a bunch of other libraries. > >Does it run as slowly on a 366MHz machine with 256MB of RAM? That would be >a clue right there. > >Have you tried it with different operating systems? Windows 98 is going to >have a much smaller footprint than Windows Server 2003... > >"news.microsoft.com" <klammer@utanet.at> wrote in message >news:uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl... >> I've to run .net applications on a low power machine (366mhz and 96mb >ram!). >> Unfortunately this application needs about 23 seconds to startup, which >> isn't acceptable. The app uses a custom library which in turn uses >DirectX9 >> managed extensions. >> This library (assembly) contains about 10 assembly references. So I used >> 'ngen' to create native images of these assemblies. However this doesn't >> help. >> >> Are there other ways to improve the startup time? >> How can I accelerate loading assemblies? Can I disable some security >checks >> for instance? (I use the default machine configuration so far) >> Is there a way to keep assemblies loaded? >> >> Any tips, hints, and tricks are welcome. >> >> Thanks, Claus >> >> > > > -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
Thanks for 'mscorjit.dll' hint.
It seems that not all of our referenced assemblies are native images. Is there a tool that simply ngen all referenced dlls of an specified assembly? Or is there a tool that creates native images of all assemblies in the gac at least. (Getting this information out of the manifest file manually, isn't a convenient way ;-)!) Thanks for your response, Claus "Ori Gershony [MSFT]" <Ori_Gershony@online.microsoft.com> schrieb im Newsbeitrag news:H0gGnDLnDHA.2148@cpmsftngxa06.phx.gbl... [quoted text, click to view] > > Have you tried profiling your application? Things are not always what they > appear, and you never know what is actually happening at startup time until > you measure it. Beyond that, my tips would be: > > 1) Make sure you ngen all the assemblies that are used at startup > (including the application). If you see mscorjit.dll loaded into your > process, it means that you missed something (or that the application is > generating code dynamically which is an even bigger perf problem). > 2) After you profile your application, see if you can avoid loading some of > the assemblies (by deferring initialization until later, or maybe not using > them at all). Avoiding assembly loads can give you big wins. > > Good luck! > > -- Ori. > > -------------------- > >From: "Jason Smith" <jason@nospam.com> > >References: <uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl> > >Subject: Re: How to shorten startup time on low power machine? > >Date: Fri, 24 Oct 2003 21:29:02 -0600 > >Lines: 39 > >X-Priority: 3 > >X-MSMail-Priority: Normal > >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 > >Message-ID: <udIflgqmDHA.684@TK2MSFTNGP09.phx.gbl> > >Newsgroups: microsoft.public.dotnet.framework.performance > >NNTP-Posting-Host: dpc6682114093.direcpc.com 66.82.114.93 > >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl > >Xref: cpmsftngxa06.phx.gbl > microsoft.public.dotnet.framework.performance:5692 > >X-Tomcat-NG: microsoft.public.dotnet.framework.performance > > > >96 megs isn't a whole lot. Are you running into any memory thrashing? > >Check Task Manager to see if you are using more memory than is physically > >available in the machine. If so, upgrade to 128MB. > > > >It sounds like you have done most everything you can do to speed up .NET. > >But you are using not only DirectX managed extensions, but also DirectX > >underneath, plus probably a bunch of other libraries. > > > >Does it run as slowly on a 366MHz machine with 256MB of RAM? That would be > >a clue right there. > > > >Have you tried it with different operating systems? Windows 98 is going to > >have a much smaller footprint than Windows Server 2003... > > > >"news.microsoft.com" <klammer@utanet.at> wrote in message > >news:uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl... > >> I've to run .net applications on a low power machine (366mhz and 96mb > >ram!). > >> Unfortunately this application needs about 23 seconds to startup, which > >> isn't acceptable. The app uses a custom library which in turn uses > >DirectX9 > >> managed extensions. > >> This library (assembly) contains about 10 assembly references. So I used > >> 'ngen' to create native images of these assemblies. However this doesn't > >> help. > >> > >> Are there other ways to improve the startup time? > >> How can I accelerate loading assemblies? Can I disable some security > >checks > >> for instance? (I use the default machine configuration so far) > >> Is there a way to keep assemblies loaded? > >> > >> Any tips, hints, and tricks are welcome. > >> > >> Thanks, Claus > >> > >> > > > > > > > > > -- > > This posting is provided "AS IS" with no warranties, and confers no rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm > > Note: For the benefit of the community-at-large, all responses to this > message are best directed to the newsgroup/thread from which they > originated. >
[quoted text, click to view]
> We are investigating implementing such a tool for a future release of the > Net Framework. We may even automate it in the form of a service that will > generate ngen images in the background for frequently used assemblies (so > even if you didn't ngen your assemblies during setup, they will eventually > get ngened). Great idea! - Frank
Unfortunately such a tool does not exist at this time. You will have to go through your manifests and ngen the transitive closure of all your dependencies. The .Net Framework installer will automatically ngen many of the system libraries, but you will have to ngen everything else that you need when doing your setup. Note that you only need to ngen assemblies that actually get loaded into your process (it's OK to reference a non-ngened assembly that is never used). We are investigating implementing such a tool for a future release of the .Net Framework. We may even automate it in the form of a service that will generate ngen images in the background for frequently used assemblies (so even if you didn't ngen your assemblies during setup, they will eventually get ngened). -- Ori. -------------------- [quoted text, click to view] >From: "news.microsoft.com" <klammer@utanet.at> <udIflgqmDHA.684@TK2MSFTNGP09.phx.gbl> >References: <uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl> <H0gGnDLnDHA.2148@cpmsftngxa06.phx.gbl> [quoted text, click to view] >Subject: Re: How to shorten startup time on low power machine? >Date: Thu, 30 Oct 2003 18:24:57 +0100 >Lines: 111 >X-Priority: 3 >X-MSMail-Priority: Normal >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 >Message-ID: <ukohnqwnDHA.2312@TK2MSFTNGP12.phx.gbl> >Newsgroups: microsoft.public.dotnet.framework.performance >NNTP-Posting-Host: olymp.funworld.at 213.157.135.202 >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl >Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.performance:5743 >X-Tomcat-NG: microsoft.public.dotnet.framework.performance > >Thanks for 'mscorjit.dll' hint. >It seems that not all of our referenced assemblies are native images. >Is there a tool that simply ngen all referenced dlls of an specified >assembly? Or is there a tool that creates native images of all assemblies in >the gac at least. >(Getting this information out of the manifest file manually, isn't a >convenient way ;-)!) > >Thanks for your response, >Claus > >"Ori Gershony [MSFT]" <Ori_Gershony@online.microsoft.com> schrieb im >Newsbeitrag news:H0gGnDLnDHA.2148@cpmsftngxa06.phx.gbl... >> >> Have you tried profiling your application? Things are not always what >they >> appear, and you never know what is actually happening at startup time >until >> you measure it. Beyond that, my tips would be: >> >> 1) Make sure you ngen all the assemblies that are used at startup >> (including the application). If you see mscorjit.dll loaded into your >> process, it means that you missed something (or that the application is >> generating code dynamically which is an even bigger perf problem). >> 2) After you profile your application, see if you can avoid loading some >of >> the assemblies (by deferring initialization until later, or maybe not >using >> them at all). Avoiding assembly loads can give you big wins. >> >> Good luck! >> >> -- Ori. >> >> -------------------- >> >From: "Jason Smith" <jason@nospam.com> >> >References: <uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl> >> >Subject: Re: How to shorten startup time on low power machine? >> >Date: Fri, 24 Oct 2003 21:29:02 -0600 >> >Lines: 39 >> >X-Priority: 3 >> >X-MSMail-Priority: Normal >> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 >> >Message-ID: <udIflgqmDHA.684@TK2MSFTNGP09.phx.gbl> >> >Newsgroups: microsoft.public.dotnet.framework.performance >> >NNTP-Posting-Host: dpc6682114093.direcpc.com 66.82.114.93 >> >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl >> >Xref: cpmsftngxa06.phx.gbl >> microsoft.public.dotnet.framework.performance:5692 >> >X-Tomcat-NG: microsoft.public.dotnet.framework.performance >> > >> >96 megs isn't a whole lot. Are you running into any memory thrashing? >> >Check Task Manager to see if you are using more memory than is physically >> >available in the machine. If so, upgrade to 128MB. >> > >> >It sounds like you have done most everything you can do to speed up .NET. >> >But you are using not only DirectX managed extensions, but also DirectX >> >underneath, plus probably a bunch of other libraries. >> > >> >Does it run as slowly on a 366MHz machine with 256MB of RAM? That would >be >> >a clue right there. >> > >> >Have you tried it with different operating systems? Windows 98 is going >to >> >have a much smaller footprint than Windows Server 2003... >> > >> >"news.microsoft.com" <klammer@utanet.at> wrote in message >> >news:uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl... >> >> I've to run .net applications on a low power machine (366mhz and 96mb >> >ram!). >> >> Unfortunately this application needs about 23 seconds to startup, which >> >> isn't acceptable. The app uses a custom library which in turn uses >> >DirectX9 >> >> managed extensions. >> >> This library (assembly) contains about 10 assembly references. So I >used >> >> 'ngen' to create native images of these assemblies. However this >doesn't >> >> help. >> >> >> >> Are there other ways to improve the startup time? >> >> How can I accelerate loading assemblies? Can I disable some security >> >checks >> >> for instance? (I use the default machine configuration so far) >> >> Is there a way to keep assemblies loaded? >> >> >> >> Any tips, hints, and tricks are welcome. >> >> >> >> Thanks, Claus >> >> >> >> >> > >> > >> > >> >> >> -- >> >> This posting is provided "AS IS" with no warranties, and confers no >rights. >> Use of included script samples are subject to the terms specified at >> http://www.microsoft.com/info/cpyright.htm >> >> Note: For the benefit of the community-at-large, all responses to this >> message are best directed to the newsgroup/thread from which they >> originated. >> > > > -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
You can easily write a script for the second part,
run "gacutil -l", get all the assemblies, then run ngen on each one. ngen works on file path as well as assembly name, as long as the assembly can be found by normal probing rule. for example, try "ngen system,Version=1.0.5000.0,Culture=neutral,PublicKeyToken=b77a5c561934e089" [quoted text, click to view] "news.microsoft.com" <klammer@utanet.at> wrote in message news:ukohnqwnDHA.2312@TK2MSFTNGP12.phx.gbl... > Thanks for 'mscorjit.dll' hint. > It seems that not all of our referenced assemblies are native images. > Is there a tool that simply ngen all referenced dlls of an specified > assembly? Or is there a tool that creates native images of all assemblies in > the gac at least. > (Getting this information out of the manifest file manually, isn't a > convenient way ;-)!) > > Thanks for your response, > Claus > > "Ori Gershony [MSFT]" <Ori_Gershony@online.microsoft.com> schrieb im > Newsbeitrag news:H0gGnDLnDHA.2148@cpmsftngxa06.phx.gbl... > > > > Have you tried profiling your application? Things are not always what > they > > appear, and you never know what is actually happening at startup time > until > > you measure it. Beyond that, my tips would be: > > > > 1) Make sure you ngen all the assemblies that are used at startup > > (including the application). If you see mscorjit.dll loaded into your > > process, it means that you missed something (or that the application is > > generating code dynamically which is an even bigger perf problem). > > 2) After you profile your application, see if you can avoid loading some > of > > the assemblies (by deferring initialization until later, or maybe not > using > > them at all). Avoiding assembly loads can give you big wins. > > > > Good luck! > > > > -- Ori. > > > > -------------------- > > >From: "Jason Smith" <jason@nospam.com> > > >References: <uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl> > > >Subject: Re: How to shorten startup time on low power machine? > > >Date: Fri, 24 Oct 2003 21:29:02 -0600 > > >Lines: 39 > > >X-Priority: 3 > > >X-MSMail-Priority: Normal > > >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 > > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 > > >Message-ID: <udIflgqmDHA.684@TK2MSFTNGP09.phx.gbl> > > >Newsgroups: microsoft.public.dotnet.framework.performance > > >NNTP-Posting-Host: dpc6682114093.direcpc.com 66.82.114.93 > > >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl > > >Xref: cpmsftngxa06.phx.gbl > > microsoft.public.dotnet.framework.performance:5692 > > >X-Tomcat-NG: microsoft.public.dotnet.framework.performance > > > > > >96 megs isn't a whole lot. Are you running into any memory thrashing? > > >Check Task Manager to see if you are using more memory than is physically > > >available in the machine. If so, upgrade to 128MB. > > > > > >It sounds like you have done most everything you can do to speed up ..NET. > > >But you are using not only DirectX managed extensions, but also DirectX > > >underneath, plus probably a bunch of other libraries. > > > > > >Does it run as slowly on a 366MHz machine with 256MB of RAM? That would > be > > >a clue right there. > > > > > >Have you tried it with different operating systems? Windows 98 is going > to > > >have a much smaller footprint than Windows Server 2003... > > > > > >"news.microsoft.com" <klammer@utanet.at> wrote in message > > >news:uA6BW8VmDHA.1244@TK2MSFTNGP11.phx.gbl... > > >> I've to run .net applications on a low power machine (366mhz and 96mb > > >ram!). > > >> Unfortunately this application needs about 23 seconds to startup, which > > >> isn't acceptable. The app uses a custom library which in turn uses > > >DirectX9 > > >> managed extensions. > > >> This library (assembly) contains about 10 assembly references. So I > used > > >> 'ngen' to create native images of these assemblies. However this > doesn't > > >> help. > > >> > > >> Are there other ways to improve the startup time? > > >> How can I accelerate loading assemblies? Can I disable some security > > >checks > > >> for instance? (I use the default machine configuration so far) > > >> Is there a way to keep assemblies loaded? > > >> > > >> Any tips, hints, and tricks are welcome. > > >> > > >> Thanks, Claus > > >> > > >> > > > > > > > > > > > > > > > -- > > > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > Use of included script samples are subject to the terms specified at > > http://www.microsoft.com/info/cpyright.htm > > > > Note: For the benefit of the community-at-large, all responses to this > > message are best directed to the newsgroup/thread from which they > > originated. > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |