Size of requests FOR pages

  • Thread starter Thread starter MattC
  • Start date Start date
M

MattC

I used a trace tool (YATT) to see the size of my pages coming down the
network. The page sizes were ok coming in at about 3K per page, but I
noticed the bytes out column was 20K. Some of my users are dialup and so to
send 20K to get a 3K page is obsured.

Does anyone know any other good trace tools I can use to inspect the HTTP
transmissions both in and out?

TIA

MattC
 
Matt:
Two suggestions, not sure how helpfult hey are:

the IIS 6.0 resource kit has a neat tool called WFetch which lets
easily-enough request a resource from your website and see the entire
response stream. This should give you an idea of where the 20K are coming
from...I think you can get it from:
http://www.microsoft.com/downloads/...ee-a71a-4c73-b628-ade629c89499&displaylang=en

You should also check out some free HTTPCompression utlilities. My favorite
was http://www.blowery.org/code/HttpCompressionModule.html (free)....it can
really really improve transfer performance...

Hope this helps,
Karl
 
Karl,

Thanks for the link, I'll check that out in a second. However, I know the
amount of data in the Response, its the amount of data being sent in the
Request that interests me, this is as important as the amount coming in.

MattC
 
Matt:
Have you looked at optimizing the viewstate? Since it's a hidden field
whenever users do a postback, the viewstate (along with all other form field
values) will be submitted as part of the request.

Just another thought :)

Karl
 
Karl,

Yes this is how I noticed the size of the page going up the line. I have
persisted my viewstate to the applicaiton Cache. However this does raise
the question in my head, what is being sent back up the line.

On an ASP.NET form even if my viewstate is persisted to the server on a
postback the entire form must be sent back up the network right? Is the 20K
in a request the total size of the form being posted back to the server?

How can I see what is exactly being sent to the server, I couldn't install
WFETCH unfortunatley it gave me an error!

TIA

MattC
 
Matt,
You should be able to find out the first part of your question, is the 20K
simply the entire form, simply by looking at Request.ContentLenght...

You might also want to take a look at some of the ServerVariables (or simply
turn on tracing) which will give you a breakdown of what the request
contains and from that you can see if anything seems oddly large.

That's all I got :)

Karl
 
Well the ContentLength is always around 900bytes, so if that's all that is
coming up then I dont know why YATT is recording 20000bytes of outgoing
details?

Thanks anyways.

MattC
 
Back
Top