|
|
MSSQL
Started by mat hew at 07-21-2007 1:39 PM. Topic has 5 replies.
  
|
|
Sort Posts:
|
|
|
|
 07-21-2007, 1:39 PM
|
mat hew
Joined on 07-22-2007
Posts 2
|
|
|
Hello, I am noticing slow Umbraco Performance on my site (techdrone.com). My scenario isn't too complicated other than the fact that I'm trying to run umbraco. There is not any content... db is basically empty, etc... so it ist is just new umbraco install. Basically I'm starting from scratch... so just thought I'd mention that in case this info is useful.
Right now here is what I'm seeing:
- A slow initial page load. Approx: 20 seconds
Other things I've noticed:
- Once the page finally gets loaded then the site performs very well while it is in use.
- BUT if you /leave the site and stop using it for a while/ and then /go back to it later/... it loads slow again at this point.
So far I've only been investigating the DB performance. I changed the DB recovery model to SIMPLE and that actually did seem to help ever so slightly. I'm not positive it helped but it seems like to me the load time decreased... I'm almost positive it was taking longer than 20 seconds on average before changing to SIMPLE.
I'm curious if anyone else runs umbraco on their account and if so what is their experience with performance? Any tips or suggestions would be appreciated. I will keep investigating and try to see if there is anything within umbraco itself that could cause this... but I don't suspect that is the case since this is a fresh install. Also, I plan to run an asp.net trace sometime this weekend and maybe that might tell me if slowness is at the DB level or in the Umbraco app.
Thanks,
M@
|
|
|
|
|
Report
|
|
|
|
|
07-23-2007, 2:37 PM
|
admin
Joined on 08-10-2005
Posts 245
|
|
|
|
I am almost certian that it's not mssql related. It's most likely cost by the fact that you do not have much traffic coming to your site and your asp.net application is being recomiple all the time so your initial load will be slow and after that it'll be very fast. The best way to work around this is to 1st) have support move you to a different application pool, 2nd) Schedule your site to be visited every 30 mins or so. You can do this via the control panel very easily.
|
|
|
|
|
Report
|
|
|
|
|
07-23-2007, 6:01 PM
|
mat hew
Joined on 07-22-2007
Posts 2
|
|
|
|
Ok, that makes sense. I will do that. Thank you for the suggestions.
|
|
|
|
|
Report
|
|
|
|
|
06-14-2008, 8:37 AM
|
HOPS
Joined on 03-30-2008
Posts 8
|
|
|
|
 mat hew wrote: | Ok, that makes sense. I will do that. Thank you for the suggestions.
|
|
What you describe is common with ASP.NET applications. IIS/ASP is designed to shut down the process after a certain period after which there have been no requests. Therefore, when the next user requests the first page, the application has to be compiled and restarted which can take a while, especially if the server is loaded.
Personally, I think the default timeout of 20 minutes is a little tight. 40 minutes would be nicer. In my application, I run a server side timer to process things in the background, like sending a summary email a while after the user has stopped entering data. With the 20 minute process shutdown, it means that the maximum I can delay sending is something less than 20 minutes. I go for 15 minutes.
It's not the end of the world as if the process down shut down, the next user to access the site triggers the timer and it sends that email.
Cheers, Rob.
|
|
|
|
|
Report
|
|
|
|
|
06-15-2008, 12:18 AM
|
deanman
Joined on 04-11-2007
Posts 197
|
|
|
|
Well, just increasing the session timeout of the application does not prevent the application from being recycled. On shared hosting, the only way to keep the application 'alive' are the steps pointed out by 'admin'. However, an isolated application pool per application would be better than shared pools for several applications -- and the application should be browsed at least every 5 minutes.
I <3 WebHost4Life.com
|
|
|
|
|
Report
|
|
|
|
|
10-16-2008, 9:07 AM
|
HOPS
Joined on 03-30-2008
Posts 8
|
|
|
|
This is common with WebHost4Life. The application worker process is recycled frequently which means that ASP.NET has to recompile your web site. They haven't published their configuration settings but I've had www.whatpub.org stop the application just 5 minutes after starting - loosing the inproc session.
I suppose it's the price we pay for a very cheap hosting service.
Rob.
|
|
|
|
|
Report
|
|
|
|
|
Webhost4life Fo... » Database Relate... » MSSQL » Umbraco Performance
|
|
|
|