Load time high upon first visit is extremly slow. When the page finally loads it is super fast. We have hosted a lot of Umbraco sites without problems on the same server setup. Win 2008 Server with SQL Express.
We have used both RAZOR and XSLT. I remember some suggested that RAZOR could perhaps have some compiling issues or am I wrong.
Anybody have some suggestions on how to debug this? Or perhaps had similar experiences?
It should only be first hit of page after deployment to compile.
There have been a lot of bug fixes and improvements since 6.0.3 (also a security issue which needs patching) - i would personally look to get it up to the latest 6.1.5 before spending hours trying to find the issue. Then id look to stuff like page speed analysis and see what it holding up the load time if its not a compile latency.
Ive done one and there was something to do with the htmlagaility dll in the config. Best thing is to make a dupe, do the upgrade and then use something like winmerge to compare the config files which you can do on a directory so its quick and easy to make sure none of your settings have changed.
The download page has all the instructions on the upgrade. But do it on another test site first and it takes away the pain of something going wrong. Thats what i always do with a big upgrade.
This is also a decent tool for looking at the speed:
Are you using razor macros with WebForms templates or Mvc?
Also have you used the Umbraco debug and trace mode (or mini profiler for Mvc) to find out what is taking the time to execute?
If you are using razor macros, I would look for usages of Descendants as this method is quite inefficient and can generally be replaced with the XPath method. If you are using Mvc then there is no problem with using the Descendants method.
Load time high upon first visit
We have created a site in Umbraco V6.0.3.
http://zoombyzoom.dk
Load time high upon first visit is extremly slow. When the page finally loads it is super fast. We have hosted a lot of Umbraco sites without problems on the same server setup. Win 2008 Server with SQL Express.
We have used both RAZOR and XSLT. I remember some suggested that RAZOR could perhaps have some compiling issues or am I wrong.
Anybody have some suggestions on how to debug this? Or perhaps had similar experiences?
It should only be first hit of page after deployment to compile.
There have been a lot of bug fixes and improvements since 6.0.3 (also a security issue which needs patching) - i would personally look to get it up to the latest 6.1.5 before spending hours trying to find the issue. Then id look to stuff like page speed analysis and see what it holding up the load time if its not a compile latency.
Can you setup another install of the site and do the upgrade (on a duplicate database etc) and see if the problem is still there?
The upgrade from 6.0.3 -> 6.1.5 should be pretty easy, right?
Any changes to the config files?
Ive done one and there was something to do with the htmlagaility dll in the config. Best thing is to make a dupe, do the upgrade and then use something like winmerge to compare the config files which you can do on a directory so its quick and easy to make sure none of your settings have changed.
The download page has all the instructions on the upgrade. But do it on another test site first and it takes away the pain of something going wrong. Thats what i always do with a big upgrade.
This is also a decent tool for looking at the speed:
http://tools.pingdom.com/fpt/#!/cnoyis/http://zoombyzoom.dk/
I ran it against your site and it came back pretty decent.
help docs:
http://our.umbraco.org/documentation/Installation/Upgrading/general
this one details the config change but not sure if your site will already have it..?
http://our.umbraco.org/contribute/releases/613
Hi Henning,
Are you using razor macros with WebForms templates or Mvc?
Also have you used the Umbraco debug and trace mode (or mini profiler for Mvc) to find out what is taking the time to execute?
If you are using razor macros, I would look for usages of Descendants as this method is quite inefficient and can generally be replaced with the XPath method. If you are using Mvc then there is no problem with using the Descendants method.
Thanks,
Jeavon
is working on a reply...