Re: Buffering issue
From: Egbert Nierop \(MVP for IIS\) (egbert_nierop_at_nospam.invalid)
Date: 10/06/04
- Next message: shtemmer: "IIS Crashing"
- Previous message: Tom Kaminski [MVP]: "Re: Scheduled Backup w/ WebDAV???"
- In reply to: Scott Hamlin: "Re: Buffering issue"
- Next in thread: Ken Schaefer: "Re: Buffering issue"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 6 Oct 2004 14:30:01 +0200
"Scott Hamlin" <srxyz2003@go.com> wrote in message
news:1097065054.KaMZNYxhrrgvESokymlLiA@teranews...
> I'll restate my question without the background information to confuse
> anyone: Are there any settings on IIS 6.0 or Windows 2003 that would
> affect
> buffering? We have a web application. The application works fine on test,
> but not on production.
>
> Ken, the Buffer.Flush may work for us. I'll test it out. But, I am curious
> as to why, when the buffer is turned off on one server it works, but on
> another server it does not.
It can become terribly slow because the connection is going over the
internet instead of a local intranet.
If you turn off the buffer, the Content-Size buffer is not sent as well and
socketpooling does not work (this last thing is a quick thought not 100%
sure).
It also can be caused by a badly tested ISAPI filter.
Or the server is set into win2000 compatibility mode.
Regards,
> "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
> news:eOjsza0qEHA.2948@TK2MSFTNGP11.phx.gbl...
>> Hi,
>>
>> There is not enough information in your post to make any sort of
> definitive
>> statement as to what might be causing the problem.
>>
>> a) I don't see from your description why you need to turn buffering off.
>> Buffering improves IIS performance in terms of placing data onto the wire
> in
>> the most optimal way. Client side operations should not be impacted by
>> buffering settings. Usually buffering would be turned off if you need to
>> send something to the client now (so the client knows something is
> happening
>> and doesn't give up waiting), then perform further operations on the
> server,
>> and then send another response to the client at some later time. You can
>> also accomplish this by leaving buffering on, and using Response.Flush in
>> your ASP code.
>>
>> b) You don't tell us where the delay is occuring. Is IIS taking a long
> time
>> to process the code? Is it taking a long time for the output to make it
> from
>> IIS (after IIS has finished processing) to the client? Is the client
> taking
>> a long time to process the code that it is receiving? Examing the IIS log
>> files might shed some light on the first point, using a network trace
> (like
>> Ethereal) will shed some light on the second, and from that you can also
>> deduce how long IE is taking to render whatever you're doing.
>>
>> Cheers
>> Ken
>>
>>
>> "Scott Hamlin" <srxyz2003@go.com> wrote in message
>> news:1097006817.ToVFTGHeJeMt0FX6wiBdRg@teranews...
>> > We have recently rolled out an application from a test environment to
>> > production. Because of a piece of code we use that updates records from
>> > the
>> > server side into another window using JavaScript, we have turned
> buffering
>> > off on a particular page. On testing, this has not caused an issue. On
>> > production, however, the page loads incredibly slow, and that is before
>> > the
>> > user has actually done anything to invoke the more complex pieces of
>> > the
>> > application. Are there any IIS or web appliation properties (or other
>> > Windows 2003 settings) that I should be on the lookout for? I have
> searchd
>> > through the IIS settings, but nothing jumped out at me.
>> >
>> > Thank you,
>> > Scott
>> >
>> >
>>
>>
>
>
- Next message: shtemmer: "IIS Crashing"
- Previous message: Tom Kaminski [MVP]: "Re: Scheduled Backup w/ WebDAV???"
- In reply to: Scott Hamlin: "Re: Buffering issue"
- Next in thread: Ken Schaefer: "Re: Buffering issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|