Last week i installed a copy of 4.7.1.1 for a collegue of mine on his domain @ surftown.
It's running pretty well and performance is good, except during the first visit of the day.
Ever since he comlained about the long load times i decided to visit it more often to check on it. It seems like the first run of the day always recompiles (load time is similiar to the first run after install) Umbraco.
Obviously this wont work if the first visitor is a customer.
Surftown cant help and insists its a software problem.
Is there a setting on the server or in Umbracos web.config that makes the compiled code "timeout" or similiar?
Hope you can help, and thx for all your hard work :)
Are you sure it's actually being recompiled? As Jeroen alludes to, it could be the application pool getting recycled (the standard App Pool Recycling setting for IIS 6/7 is something like 1740 minutes = 1.2 days); this could cause a bit of a performance hit on the first visit while memory is being mapped, so to speak.
Of course, exceeding a number values (recycle timeout, max request count, etc.) could also cause this threshold to be hit, and hence initiate a recycle.
You can extend the time and other threshold values so that this happens much less frequently than every day - but this really depends on your system - for instance, that will be no good if your site is memory, or cycle hungry and is force-recycled prior to meeting your specified thresholds. Since your host is denying the problem, though, you don't seem to have that much control and so it's not as easy as tweaking the settings and analysing over some time.
Unfortunately the problem can't be completely removed (at least not yet), only delayed and made to seem removed. It's almost analogous to grumpy humans on any given Monday. It's the usual thing.
Optimising your site could yield some improvement, too, if you're sure to minimise memory usage and application init complexity and whatnot.
4.7.1.1 "recompiles" daily
Hey all,
Last week i installed a copy of 4.7.1.1 for a collegue of mine on his domain @ surftown.
It's running pretty well and performance is good, except during the first visit of the day.
Ever since he comlained about the long load times i decided to visit it more often to check on it. It seems like the first run of the day always recompiles (load time is similiar to the first run after install) Umbraco.
Obviously this wont work if the first visitor is a customer.
Surftown cant help and insists its a software problem.
Is there a setting on the server or in Umbracos web.config that makes the compiled code "timeout" or similiar?
Hope you can help, and thx for all your hard work :)
Here at our company we recycle our app pool every night. This causes the website to "recompile". Maybe Surftown also does that.
Jeroen
Are you sure it's actually being recompiled? As Jeroen alludes to, it could be the application pool getting recycled (the standard App Pool Recycling setting for IIS 6/7 is something like 1740 minutes = 1.2 days); this could cause a bit of a performance hit on the first visit while memory is being mapped, so to speak.
Of course, exceeding a number values (recycle timeout, max request count, etc.) could also cause this threshold to be hit, and hence initiate a recycle.
How are you handling it on your servers? Do you just accept the poor performance for that unlucky user or can you set something up to "keep it alive"?
You can extend the time and other threshold values so that this happens much less frequently than every day - but this really depends on your system - for instance, that will be no good if your site is memory, or cycle hungry and is force-recycled prior to meeting your specified thresholds. Since your host is denying the problem, though, you don't seem to have that much control and so it's not as easy as tweaking the settings and analysing over some time.
Unfortunately the problem can't be completely removed (at least not yet), only delayed and made to seem removed. It's almost analogous to grumpy humans on any given Monday. It's the usual thing.
Optimising your site could yield some improvement, too, if you're sure to minimise memory usage and application init complexity and whatnot.
is working on a reply...