Deevo
  • Posts: 2
  • Joined: 24/09/2011
I have recently installed YAF forum on my web server and noticed the intial load of YAF to be very slow. Once the forum has been visited it runs very fast but the first page takes a very long time to load. Other than that it seems to be working fine even though there is no activity on the forums.

You can visit my forums at http://forum.mastersofthemat.com 

Any help would be appreciated thanks in advance
Sponsor
squirrel
  • Posts: 925
  • Joined: 14/01/2010
That is most likely the 'application startup' when IIS is initializing your application pool and pre-loading the YAF ASP.NET application files into memory. This is not a YAF issue more an IIS/ASP.NET configuration issue. Any ASP/ASP.NET application when initially started will take longer, as IIS 'starts' the application just like starting a program on your Windows desktop...
If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
Deevo
  • Posts: 2
  • Joined: 24/09/2011
I thought the application pool is created once the application is started ...ie "click the play button on the website in IIS". So if no one goes to the forums for a half an hour the pool gets recreated the next time someone visits it? I am not ruling out an IIS problem, there must be some settings I have wrong, any ideas?
squirrel
  • Posts: 925
  • Joined: 14/01/2010
Originally Posted by: Deevo

I thought the application pool is created once the application is started ...ie "click the play button on the website in IIS". So if no one goes to the forums for a half an hour the pool gets recreated the next time someone visits it? I am not ruling out an IIS problem, there must be some settings I have wrong, any ideas?



The pool is 'created' (with it's settings and configuration/identity) but it is not 'launched' until a request comes into the web server. By default, IIS shuts down any inactive App Pools in 20 minutes of no activity (no requests). It also attempts to detect failures and dead-locked pools and recycles them as needed. You can override the IIS shutdown period for an application pool in it's configuration, but if you set a pool to be active continuously then it is recommended you at least allow it to recycle (restart) the pool every so often. On my servers I lease out, we recycle most of ours every 24 hours - ones with 'poorly written applications' get recycled every 6 hours to maintain overall server availability as well as to keep resource consumption at a dull-roar. Poorly written applications will consume memory and resources and can bring a server to a crawl if not monitored.

If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
Users browsing this topic
    Forum Jump  
    • You cannot post new topics in this forum.
    • You cannot reply to topics in this forum.
    • You cannot delete your posts in this forum.
    • You cannot edit your posts in this forum.
    • You cannot create polls in this forum.
    • You cannot vote in polls in this forum.

    About Us

    The YAF.NET is an open source .NET forum project. YAF.NET is supported by an team of international developers who are build community by building community software.

    Powered by Resharper Donate with PayPal button

    Project Twitter Updates

    Copyright © YetAnotherForum.NET & Ingo Herbote. All rights reserved