CODEWITHSUNDEEP
asp.netiis-7umbraco
Funky
Funky

Reputation: 13608

My site is taking a very long time to load, what can I do to investigate the issue?

my site is ASP.NET,C#, .net 4, using Umbraco 4, IIS 7.5 it has been working great for months but suddenly its taking ages just to load a single page and mostly not loading at all.

The DB looks fine,

I've restarted the site,

recycled the APP pool,

looked in the logs, it just looks like jibberish

Does anyone have any ideas as to how I can investigate further. No I am not asking you to fix my site or tell me why it is not working, I just want to know other methods for investigating the problem so I can get to the bottom of the issue.

IIS LOG:

http://pastebin.com/msjzty7m

Thanks

Upvotes: 3

Views: 2273

Answers (4)

Aristos
Aristos

Reputation: 66641

This is not loading at all... the online tools can not help, you need to investigate whats happens on the server.

The tools for that is the process explorer from sysinternals to see what is running slow your server, then the autoruns to see what you loading with out your knowledge and also slow down your system, and the tcpView to see who is connected to your server.

Upvotes: 0

The Angry Saxon
The Angry Saxon

Reputation: 792

My first guess would be it is infact a data issue. Not that it's taking a long time to grab the data but to process it. I've had a few times now where a page is around 138Kb but took over 3 seconds to wait for the page before rendering. Basically this was cause it was running a 3 tier repeater (repeater inside repeater inside repeater) to create the menu system. So even though the site wasn't big it was taking time processing this menu before sending it out.

Suggestions from me would be to comment out anything new that you've added before this date and bring stuff back in slowly till you find the problem part. After that you can look at caching. And if it's a module (.ascx) use @ Output Caching and that could help.

Upvotes: 1

gustavodidomenico
gustavodidomenico

Reputation: 4681

I have a couple of suggestions:

  1. Set up the ELMAH error log and take a look if some unhandled expcetions.
  2. Set up mini profiler, maybe it is a bottle neck inside a new added script.
  3. Use google PageSpeed Insights to analyze your pages.

Upvotes: 1

Bazzz
Bazzz

Reputation: 26922

Use Google Pagespeed Insights to see where the problems might be.

Upvotes: 1

Related Questions