I am using IIS7 on Windows Server 2008 / Vista Ultimate SP1 / 1GB RAM,
I create an ASP.NET 3.5 file named Default.aspx with Visual Studio 2008,
I have a problem, my site is rarely accessed, everytime I try to access it, it take lots of time for my browser to load it, however, if I access it again later in a short time, it load much faster than 1st access. If I access it tomorrow, it takes quite
long.
How can I configure IIS7 to store that page on memory so that it could be accessed fastest even if it's rarely accessed by visitors?
This has nothing to with IIS. ASP.NET is compiled on first access, cached for 20 minutes and discarded if not accessed again. Precompile the pages/app or access them more frequently. Design your app so pages are accessed frequently, even if the displayed
data isn't. You can find out how to do this at www.asp.net, same login as here.
I don't know specifically for 2008, but with IIS6 you would have to tweak the application pool for the website. By default with IIS6 the worker processes would shut down after 20 minutes of inactivity or after 1740 minutes no matter what. If you want to
keep it fresh you could disable the idle timeout and disable the recycle time or increase it to more than 29h.
Here is how to set the idle timeout. The default is 20 minutes. As far as disabling, I'm 99% sure setting to zero is the same as IIS 6 unchecking the option.
IIS Manager > Expand the tree control > application pools > right click on your application pool, select properties > Select Recycling. Turn off Regular time intervals. The default is 1740 minutes (29 hours).
Actualy, what you want to disable is ApplicationPool idle timeout - by default set to 20 minutes. You can do this by going to 'advanced settings' for an AppPool, and setting it to 0.
duynghia
3 Posts
IIS7's low performance on rarely accessed ASP.NET 3.5 files
Mar 15, 2008 10:55 AM|LINK
Hello everyone,
I am using IIS7 on Windows Server 2008 / Vista Ultimate SP1 / 1GB RAM,
I create an ASP.NET 3.5 file named Default.aspx with Visual Studio 2008,
I have a problem, my site is rarely accessed, everytime I try to access it, it take lots of time for my browser to load it, however, if I access it again later in a short time, it load much faster than 1st access. If I access it tomorrow, it takes quite long.
How can I configure IIS7 to store that page on memory so that it could be accessed fastest even if it's rarely accessed by visitors?
Thank you,
Duy Nghia
jeff@zina.co...
3379 Posts
MVP
Moderator
Re: IIS7's low performance on rarely accessed ASP.NET 3.5 files
Mar 15, 2008 08:27 PM|LINK
This has nothing to with IIS. ASP.NET is compiled on first access, cached for 20 minutes and discarded if not accessed again. Precompile the pages/app or access them more frequently. Design your app so pages are accessed frequently, even if the displayed data isn't. You can find out how to do this at www.asp.net, same login as here.
Jeff
pbz
5 Posts
Re: IIS7's low performance on rarely accessed ASP.NET 3.5 files
Mar 15, 2008 10:46 PM|LINK
I don't know specifically for 2008, but with IIS6 you would have to tweak the application pool for the website. By default with IIS6 the worker processes would shut down after 20 minutes of inactivity or after 1740 minutes no matter what. If you want to keep it fresh you could disable the idle timeout and disable the recycle time or increase it to more than 29h.
steve schofi...
5681 Posts
MVP
Moderator
Re: IIS7's low performance on rarely accessed ASP.NET 3.5 files
Mar 15, 2008 11:51 PM|LINK
I second this suggestion.
Steve Schofield
Windows Server MVP - IIS
http://iislogs.com/steveschofield
http://www.IISLogs.com
Log archival solution
Install, Configure, Forget
duynghia
3 Posts
Re: IIS7's low performance on rarely accessed ASP.NET 3.5 files
Mar 16, 2008 12:52 AM|LINK
Ok, how can I increase 20-minute limit, or disable the idle timeout or disable recycle time?
Please tell me more details about it
Thank you
steve schofi...
5681 Posts
MVP
Moderator
Re: IIS7's low performance on rarely accessed ASP.NET 3.5 files
Mar 16, 2008 04:10 AM|LINK
Here is how to set the idle timeout. The default is 20 minutes. As far as disabling, I'm 99% sure setting to zero is the same as IIS 6 unchecking the option.
http://technet2.microsoft.com/windowsserver2008/en/library/8a96bbb8-4c28-44e8-ac91-5252cb1175501033.mspx?mfr=true
Here is how to disable recycle options
IIS Manager > Expand the tree control > application pools > right click on your application pool, select properties > Select Recycling. Turn off Regular time intervals. The default is 1740 minutes (29 hours).
Steve Schofield
Windows Server MVP - IIS
http://iislogs.com/steveschofield
http://www.IISLogs.com
Log archival solution
Install, Configure, Forget
bills
433 Posts
Microsoft
Re: IIS7's low performance on rarely accessed ASP.NET 3.5 files
Jul 02, 2008 03:14 PM|LINK
Actualy, what you want to disable is ApplicationPool idle timeout - by default set to 20 minutes. You can do this by going to 'advanced settings' for an AppPool, and setting it to 0.
Bill Staples
Product Unit Manager, IIS
blog: http://blogs.iis.net/bills
duynghia
3 Posts
Re: IIS7's low performance on rarely accessed ASP.NET 3.5 files
Jul 04, 2008 09:23 AM|LINK
GREAT!!! Thank YOU so much!!!