Network question

[tshad]

I am finding that our site typically responds pretty well.

But sometimes I will be going to the logon page, which should load fast, and
I will have to wait about 20 seconds before it displays.

How would I go about finding out if the problem is network related (our
network normally is not normally in heavy use) or is the web server taking
time sending out the page or some other issue?

Thanks,

Tom

 

[Laurent Bugnion]

Hi,

I am finding that our site typically responds pretty well.

But sometimes I will be going to the logon page, which should load fast, and
I will have to wait about 20 seconds before it displays.

How would I go about finding out if the problem is network related (our
network normally is not normally in heavy use) or is the web server taking
time sending out the page or some other issue?

Thanks,

Tom

I see different approaches:

1) Logging. At first, enable server-side logging to see when the request
arrives, when it is processed (add logging in your code), and when it is
sent back to the client. If everything is normal on the server, you can
try to use client-side logging, but it's a bit trickier. I do
client-side logging in two ways:
- Using a web service to create the messages on the client, send them to
the server and log them to the same log file as the server-side logging
- Using JavaScript to write client-side files (but that only works if
certain permissions are set).

For client-side file writing, see
http://www.galasoft-lb.ch/myjavascript/CExplorer/index.html

2) Use a HTTP analyzer (for example the excellent Fiddler) to monitor
your traffic.

3) Test in different configurations, with different loads (number of
clients, number of requests) and try to find the smallest common
denominator...

Most probably a combination of 1,2,3 will bring you the answer...

HTH,
Laurent

 

[tshad]

Hi,


I see different approaches:

1) Logging. At first, enable server-side logging to see when the request
arrives, when it is processed (add logging in your code), and when it is
sent back to the client. If everything is normal on the server, you can
try to use client-side logging, but it's a bit trickier. I do client-side
logging in two ways:

I am logging certain things to my Sql Server, but that might negate the
test.

How would I write logging to tell when a page arrives, processed and sent
back?

- Using a web service to create the messages on the client, send them to
the server and log them to the same log file as the server-side logging
- Using JavaScript to write client-side files (but that only works if
certain permissions are set).

For client-side file writing, see
http://www.galasoft-lb.ch/myjavascript/CExplorer/index.html

2) Use a HTTP analyzer (for example the excellent Fiddler) to monitor your
traffic.

I am going to check this.

I assume that Fiddler is loaded onto the Web Server.

Am I able to administer and analyse the data from my workstation?

Thanks,

Tom

 

[Laurent Bugnion]

Hi,

I am logging certain things to my Sql Server, but that might negate the
test.

How would I write logging to tell when a page arrives, processed and sent
back?

Actually, I meant using the built-in ASP.NET logging possibilities
(sorry, it's actually called Tracing), which are giving you a lot already.

Enabling the Trace attribute in the Page directive allow to output a lot
of information to the console or even to the page itself, which can be
very helpful.

You can also enable tracing for the whole site using the <trace> section
in the web.config file.

Additionally, you can add trace messages from your code-behind using the
Page.Trace property and its Write method.

I am going to check this.

I assume that Fiddler is loaded onto the Web Server.

No, Fiddler is actually placed between the client and the server,
typically on one the same computer as one of the web clients. It
displays all HTTP traffic occuring between the web client and the web
server.

Am I able to administer and analyse the data from my workstation?

Thanks,

Tom

Yes.

HTH,
Laurent