CODEWITHSUNDEEP
asp.net
Ryan
Ryan

Reputation: 18129

ASP.NET Load times

I have a ASP.NET Project, v3.5 in VB.NET, that I'm working on. On my home computer pages load pretty much instantaneously when clicking something, but on my work computer (which is a much faster computer) all pages take about one second to load, regardless of the content being generated (like its on a timer or something). Why is this or how can I go about figuring out why the load time is being delayed on my work computer?

Thanks for your input.

SOLVED - The issue was the IPv6 issue with FireFox. I turned it off and everythings grand now. Thanks everyone for your input, definitely good advise for tracking down more serious performance issues, which will come in handy later, just not for this issue. Thanks!

Upvotes: 1

Views: 234

Answers (5)

D'Arcy Rittich
D'Arcy Rittich

Reputation: 171559

Using Firebug slows down the loading of web pages, especially CSS rendering. Try disabling Firebug to see if that fixes your problem.

Upvotes: 0

RichardOD
RichardOD

Reputation: 29157

Where I work we have firewall issues connecting to crl.microsoft.com.

Trying adding this to your hosts file:

127.0.0.1 crl.microsoft.com

Then restart IIS.

Upvotes: 0

Adam Markowitz
Adam Markowitz

Reputation: 13127

There are a number of things you can do to investigate performance problems/differences:

  1. You mention the 'same exact database'. If it is a local database at home and you are hitting your home database from your work machine, that may account for the latency.
  2. Use Fiddler for measuring web traffic. This can help determine if it is a server or client issue.
  3. Use Firebug with Firefox. Look at the NET tab and/or the javascript profiling on the Console tab to determine whether it is a javascript issue, or a server issue.
  4. Turn on ASP.NET tracing in your web.config to check timings in your server side code.

Upvotes: 0

alex
alex

Reputation: 953

Is the SQL Server local in both cases?

One thing you could do would be to run a Trace to see where the delays (if any) are within the actual ASP.NET process...

<configuration>
    <appSettings/>
    <connectionStrings/>
    <system.web>
        <compilation debug="false" />
        <authentication mode="Windows" />
      <trace enabled ="true" pageOutput ="false" requestLimit ="20" traceMode ="SortByTime " />        
    </system.web>
</configuration>

Upvotes: 1

John Sheehan
John Sheehan

Reputation: 78152

Assuming you're using Firefox, it could be related to this issue with IPv6 support in FF.

Upvotes: 2

Related Questions