Dear All,
We have a client application that takes 15 secs to launch after the
machine has been rebooted...now if I close the application and start
again it takes 6 secs...what is the mystery?
Does this mean:
1. That 9 secs is CLR starting time?
2. OR it is the GAC loading of .net framework dlls?
Is there some other method than NGen where I can load my dlls in
memory so that they can be shared across application domains...putting
dlls in GAC ensures sharing but each time I open an Application does
it compile the dll according to Application domain?
I tired to check this via PerfMon .NET CLR Loading
.NET CLR Loading(_Global_)\Current appdomains"
.NET CLR Loading(_Global_)\Current Classes Loaded"
.NET CLR Loading(_Global_)\Total Classes Loaded"
.NET CLR Loading(_Global_)\Current appdomains"
But could not find a key that says the assembly has been loaded
twice...
How can I pin assemblies so that they can be compiled in memory and
shared across application domains...
Please help...
TALIA
Many Regards
Jack
Richard Blewett [DevelopMentor] - 28 Oct 2004 08:35 GMT
I think you're just seeing the result of the second run having cache-hit success with data that is now in the page cache. The first time the application is run everything has to be loaded from disk.
Regards
Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog
Dear All,
We have a client application that takes 15 secs to launch after the
machine has been rebooted...now if I close the application and start
again it takes 6 secs...what is the mystery?
Does this mean:
1. That 9 secs is CLR starting time?
2. OR it is the GAC loading of .net framework dlls?
Jack Wright - 29 Oct 2004 05:24 GMT
Thanks Richard,
How do I cache my assemblies everytime my client restarts his
machine? I cannot use NGen as it requires Admin rights...
What is getting cached? My assemblies or .net assemblies?
Just doing assembly.Load("myassembly.dll") does not compile the
assembly...right? How do I trigger compiling of my assembly
programatically?
Please help...
TALIA
Many Regards
Jack
Phil Wilson - 29 Oct 2004 15:52 GMT
A profiler might help you see where the time is going. You seem to be
assuming it's all JIT and maybe assembly loading, but are you sure?

Signature
Phil Wilson
[Microsoft MVP-Windows Installer]
> Dear All,
> We have a client application that takes 15 secs to launch after the
[quoted text clipped - 26 lines]
> Many Regards
> Jack