Hi,

As this article (http://msdn2.microsoft.com/en-us/magazine/cc163655.aspx)
mentions, there is a cold and warm start time for managed apps. I'm running a
few .net 2.0 winforms apps on my desktop (XP) and until last week, I had the
expected cold followed by warm time. Now, my cold and "warm" times are about
identical. I don't know what changed. It could be something else that's
running in memory and being a hog, but I'm wondering if there is some CLR
switch that says "disable warm starts" that I can look at?

Thanks...

-Ben

benji <(E-Mail Removed)> wrote:
> As this article (http://msdn2.microsoft.com/en-us/magazine/cc163655.aspx)
> mentions, there is a cold and warm start time for managed apps. I'm running a
> few .net 2.0 winforms apps on my desktop (XP) and until last week, I had the
> expected cold followed by warm time. Now, my cold and "warm" times are about
> identical. I don't know what changed. It could be something else that's
> running in memory and being a hog, but I'm wondering if there is some CLR
> switch that says "disable warm starts" that I can look at?

It's not the the CLR is doing anything special (as I understand it) -
just that the Windows file cache will make it a lot quicker to load
things the second time.

Chances are there's some service or start-up app which is using .NET.
It may be starting up and then shutting down again, but if it's loaded
the CLR at some point, the cache is likely to have kept those pages.

--
Jon Skeet - <(E-Mail Removed)>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
World class .NET training in the UK: http://iterativetraining.co.uk