I've got an Umbraco website which is running on 6.2.4 and from time to time it's really slow. Both in frontend of the website as in the Umbraco backoffice. There is nothing in the logs to be found. There is nothing in our custom code which could make it slow.
Any suggestions in how I could research this? Is it possible to enable miniprofiler in the backoffice?
I'm running Umbraco 6.2.4. I've upgraded from 6.1.6 because that was already slow, but 6.2.4 still has the same problem. I haven't checked if the CPU goes up. Will do that :-).
How many content nodes in your implementation? Are we talking tens, hundreds or thousands of nodes? What is your backend storage? I'm assuming your data is stored on a separate SQL Server and not SQL CE.. but would like to hear more detail on that.
Since you're going to monitor CPU, Memory and Disk IO during slow times, I don't think it would hurt to run a profile trace on your SQL instance to try and find any bottlenecks or table scans caused by any inefficient queries.
Umbraco website sometimes slow
Hello,
I've got an Umbraco website which is running on 6.2.4 and from time to time it's really slow. Both in frontend of the website as in the Umbraco backoffice. There is nothing in the logs to be found. There is nothing in our custom code which could make it slow.
Any suggestions in how I could research this? Is it possible to enable miniprofiler in the backoffice?
Jeroen
Hi Jeroen,
Which version of Umbraco ? And how is your server doing with CPU and memory when the site is slow ?
Dave
I'm running Umbraco 6.2.4. I've upgraded from 6.1.6 because that was already slow, but 6.2.4 still has the same problem. I haven't checked if the CPU goes up. Will do that :-).
Jeroen
Hi Jeroen,
How many content nodes in your implementation? Are we talking tens, hundreds or thousands of nodes? What is your backend storage? I'm assuming your data is stored on a separate SQL Server and not SQL CE.. but would like to hear more detail on that.
Since you're going to monitor CPU, Memory and Disk IO during slow times, I don't think it would hurt to run a profile trace on your SQL instance to try and find any bottlenecks or table scans caused by any inefficient queries.
John
Hi Jeroen,
Just a couple of ideas:
Doing any crazy iterating in XSLT files? Maybe using the double-slash (descendant::) axis more than a couple of places?
Other posts to look at (if it's the XSLT):
/Chriztian
Can also add to Chriztians ideas:
is working on a reply...