I have a deployed site. And the web site is incredibly slow. I can't understand why. This is not normal. I feel a little slowness when I run it as a local. But this slowness is not the same as the deployed version. I'm doing this when I'm navigating through the page. Is this an incorrect use?
I don’t think your example would be the cause of what you are experiencing.
I think you should take a look on where you are traversing through you content tree.
Looking at your main menu would be a good place to start.
I scanned my code as you said. There's no problem. I don't understand where the problem ? Can't I research what Umbraco is doing in the backend or what could be causing it?
Try activating the miniprofiler and then load your frontpage.
That should give you an indication on where to look and what calls is too expensive.
This blogpost describes how to activate the miniprofiler
Could you show how you are looping over your navigation?
Excessive use of CurrentPage.Descendants could be rather expensive if you have a lot of nodes.
Try profiling your slow pages. You'll need to have debugging in web.config enabled (ie. debug='true') and then you can append the following query string to your URL to open the profiler:
I think the whole problem stems from the header part. Because all the routing menus are located in the header partial. I would show you if you want to see the header partial.
I doubt it's going to make a big difference, but he could definitely remove the ToList() and then simply use a foreach statement to iterate the items collection.
Why my deployed umbraco website is very slow?
Hi all,
I have a deployed site. And the web site is incredibly slow. I can't understand why. This is not normal. I feel a little slowness when I run it as a local. But this slowness is not the same as the deployed version. I'm doing this when I'm navigating through the page. Is this an incorrect use?
There's more like that. Do you think that could be the cause?
I'm using Umbraco 7. Database comes from the remote server. You can check. parketin.com
Do you have any idea what might be the reason for this?
I don’t think your example would be the cause of what you are experiencing. I think you should take a look on where you are traversing through you content tree. Looking at your main menu would be a good place to start.
Hi Søren,
I scanned my code as you said. There's no problem. I don't understand where the problem ? Can't I research what Umbraco is doing in the backend or what could be causing it?
Hi Dervis,
Is the backoffice running slow aswell?
Try activating the miniprofiler and then load your frontpage.
That should give you an indication on where to look and what calls is too expensive.
This blogpost describes how to activate the miniprofiler
Could you show how you are looping over your navigation?
Excessive use of
CurrentPage.Descendants
could be rather expensive if you have a lot of nodes.There's lots of good info on this docs page too: https://our.umbraco.com/documentation/Reference/Common-Pitfalls/#querying-with-descendants-descendantsorself
Thank you very much I will examine it in detail
Try profiling your slow pages. You'll need to have debugging in web.config enabled (ie. debug='true') and then you can append the following query string to your URL to open the profiler:
eg. http://www.example.com/slowpage/?umbdebug=true
Look in top right of your page and you can see a profiler that gives you execution time of queries etc.
I did what you said. Situations look very bad. Can you lead me in this situation?
http://parketin.com/mini-profiler-resources/results?id=ef97b462-00b6-40de-bf62-2689a0284195
In most of the pages the results are like this
thank you Søren and Dan
My guess is that you are looping over something in the view Yenilikler.cshtml.
If so, could you share the foreach-loop you have in that file?
@Umbraco.Web.Mvc.UmbracoTemplatePage @inherits Umbraco.Web.Mvc.UmbracoViewPage @{ Layout = null;
Thats all.
I think the whole problem stems from the header part. Because all the routing menus are located in the header partial. I would show you if you want to see the header partial.
Sorry, only have time for a quick look, but the
var myList = items.ToList();
line might be killing it.Do you need that?
I doubt it's going to make a big difference, but he could definitely remove the
ToList()
and then simply use aforeach
statement to iterate the items collection.Many thanks to everyone, but the problem was with the server. I changed my web hosting and everything works very well.
is working on a reply...