Http transfer overly "chunky"

Hi,

we are using IIS6 with ASP.Net 1.1. Our homepage is about 180k, and
when we load it internally the performance is OK. It is however always
possible to hit the "stop" button in a browser and see only a part of
the web page. Typically that part will be 24k or 56k large.

I don't see a problem with that although I did not find other webpages
where it is possible to stop the http at such well defined chunks.

The problem is that some customers report that the page stops loading
after these chunks have been received; so they get 24k of the page and
then nothing happens for 20 seconds and then the rest of the page is
being delivered.

This seems to happen for some customers on many request, while other
customers are having no problems at all. It is not dependant on the
customer's connection speed.

Are there any settings in IIS or ASP.Net that control these chunks?

TIA for any suggestion!

Regards
DC

Re: Http transfer overly "chunky"

I think this is really specific to your application and how it is written
and configured to be processed. There are no specific feature in IIS or
ASP.Net which intentionally generates such behavior.

My guess is that you probably have Compression or Chunked-Encoding enabled
on your pages, and your large homepage has some well defined segments at the
24k or 56k threshold (maybe you are doing various calculations/SQL access or
possibly running ASP.Net modules to modify ASP.Net buffered output).

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

wrote in message
news:1153301563.635602.298700@i3g2000cwc.googlegroups.com...
> Hi,
>
> we are using IIS6 with ASP.Net 1.1. Our homepage is about 180k, and
> when we load it internally the performance is OK. It is however always
> possible to hit the "stop" button in a browser and see only a part of
> the web page. Typically that part will be 24k or 56k large.
>
> I don't see a problem with that although I did not find other webpages
> where it is possible to stop the http at such well defined chunks.
>
> The problem is that some customers report that the page stops loading
> after these chunks have been received; so they get 24k of the page and
> then nothing happens for 20 seconds and then the rest of the page is
> being delivered.
>
> This seems to happen for some customers on many request, while other
> customers are having no problems at all. It is not dependant on the
> customer's connection speed.
>
> Are there any settings in IIS or ASP.Net that control these chunks?
>
> TIA for any suggestion!
>
> Regards
> DC
>

Re: Http transfer overly "chunky"

Thank you for your reply. In the meantime we found out that your are
right and this had nothing to do with HTTP transfer. There were some
slow loading ads within the page which did cause the breaks while IE
was trying to display the page (but could not since the ads contained
some essential layout elements). Only under some connectivity
circumstances the ads were really loading that slow - so only some
users experienced it.

Regards
DC


David Wang [Msft] wrote:
> I think this is really specific to your application and how it is written
> and configured to be processed. There are no specific feature in IIS or
> ASP.Net which intentionally generates such behavior.
>
> My guess is that you probably have Compression or Chunked-Encoding enabled
> on your pages, and your large homepage has some well defined segments at the
> 24k or 56k threshold (maybe you are doing various calculations/SQL access or
> possibly running ASP.Net modules to modify ASP.Net buffered output).
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
>
> wrote in message
> news:1153301563.635602.298700@i3g2000cwc.googlegroups.com...
> > Hi,
> >
> > we are using IIS6 with ASP.Net 1.1. Our homepage is about 180k, and
> > when we load it internally the performance is OK. It is however always
> > possible to hit the "stop" button in a browser and see only a part of
> > the web page. Typically that part will be 24k or 56k large.
> >
> > I don't see a problem with that although I did not find other webpages
> > where it is possible to stop the http at such well defined chunks.
> >
> > The problem is that some customers report that the page stops loading
> > after these chunks have been received; so they get 24k of the page and
> > then nothing happens for 20 seconds and then the rest of the page is
> > being delivered.
> >
> > This seems to happen for some customers on many request, while other
> > customers are having no problems at all. It is not dependant on the
> > customer's connection speed.
> >
> > Are there any settings in IIS or ASP.Net that control these chunks?
> >
> > TIA for any suggestion!
> >
> > Regards
> > DC
> >