Last post Oct 09, 2007 10:30 AM by ruek23
Oct 02, 2007 08:16 PMfirstname.lastname@example.org|LINK
I've been trying out my site on a shared host for 2 weeks now, and a page on my site comes up on average within 2 seconds, and that is pretty fast!
However, I experienced the problem where after 20 minutes of not using my site, the first visit after that takes 10 seconds! For example,
every morning when I first come to my site, it'd be much slower.
There is a setting in IIS where you right click on my site's Application Pool, there is a setting which is the "Idle timout" checkbox. The default is with this checkbox checked, and it Shuts down the worker process after 20 min of idle time.
So I contact my web host to ask them to uncheck it, they refused to do it and saying this is by design and how IIS works.
I want a different opinion on this. If to leave the checkbox on, so it shuts down the worker process after 20 min, is this best practice? And, what bad things could happen if we uncheck it? Also, has anyone experienced this problem on your web host?
If yes, how did you get around this problem?
Oct 03, 2007 11:19 AM|ruek23|LINK
Unfortunately Web Hosting companies love to keep settings as they are. This is usually due to the fact most hosting is shared between 100's maybe 1000's of hosted sites.
The only way round is to probably get a dedicated server. This can be pricey unless you can get you and a few friends who already pay £5/$10 a month for hosting to switch to a dedicated server.
Dedicated servers with Windows not Linux will cost a fair amount depending on where you get the service from. I'm based in the UK and like to have servers based over here as it mean my target is close by. I have a virtual private server from
http://www.webfusion.co.uk/ for £35/$70 a month. the good thing about this is it's cheap.
I know its a Virtual Server but read this
If you get 7 mates or you can afford the extra its the way to go.
Anyway the reason to Shut down the worker process for web hosts is due to memory usage (COST)
Oct 09, 2007 10:14 AM|OWScott|LINK
As Andy said, it's from many hosts over subscribing to site usage. Let's say they have 1000 sites on the server but most of those are low traffic sites. If they only get 3 visitors per day, they would rather the app pool only runs for 1 hour out of the
day instead of 24 hours which frees up the memory to be used by the other sites when they get their rare visit. That setting is for the sake of the server, not the site. If you can get away with it, always turn that off for a production site since you want
it preloaded and ready to run quickly when you get visitors.
If your host won't turn that off for you, you can beat the system by writing a winforms app on your computer that visits your website every 18 minutes. (I'm sure a google search will turn up some free apps that will do this for you) That will keep it alive
and give it the fast first-hit performance that you are looking for.
Oct 09, 2007 10:30 AM|ruek23|LINK
Never thought of the winforms app to visit the site every 18mins.
Not a bad idea.