Hi,

I am evaluating your wonderful program for possible use at my historical research site at a university. I am consistently getting a 10-second delay when calling up the gallery on our Windows 2008 R2 server. Then, the link works quickly after the first time. I can go downstairs to another computer and access is fast. Then, if there is some rest period when the app is not used, the 10 second delay again occurs, but only on the first access.

Has anyone encountered this problem? Is there any way to eliminate this delay on app start up?

Thanks for any assistance.

Michael Ruiz
Professor, UNC Asheville

Thanks Roger. I played around today with settings. By disabling the idle time-out (setting time to 0 apparently is the way to do this) for gallery, asp.net4, and the default application pool, I reduced the start time from 10 seconds to about 5 seconds. I also tried disabling batch compile but that did not seem to matter. There must be something else going on. With all my regular web pages, I can access quickly. Gallery Server Pro is my first experience with an application. Everything else I have done in the past has been classic asp pages for my courses and these are posting relatively fast. I would like to get Gallery to post within 2 seconds. I will keep experimenting. Thanks for pointing me in the right direction.

Michael Ruiz
Professor, UNC Asheville

Just to add for the OP, because you are right that there is no other "reason" for the delay but there is more of an explanation. :)

For the OP, this is a known condition with .Net and has been in ASP.Net since 1.0 in 2002. In pretending to be like Java, Microsoft created the idea of an Intermediate Language, or MSIL. When you compile a .Net program, it isn't really compiled to machine code, it is compiled to MSIL. When the application first starts, the MSIL is compiled to machine code. The app pool in IIS, to better share limited resources like memory, shuts down idle applications after the configured time - and you want this; it keeps the running copy cleaned up. But the result of this shut down is that when someone access the site again, after the app pool shut down, then the MSIL is compiled again into machine code on that first access. Once the app is running then successive requests are fact because no more recompiling is required until the app pool shuts down again.

So, Roger is correct, it is the app pool. But now you know why the app pool resetting causes the delay.

Hope this helps.

Dale