.net - Does ASP.NET worker process still return data in chunks of 31kb -


does asp.net worker process still return data in chunks of 31kb

this msdn article written in may 2004 specifies following.

when using asp.net process model, asp.net worker process sends responses client, first sends them through iis in 31-kilobyte (kb) chunks. applies .net framework 1.1, change in future versions. more 31-kb chunks asp.net has send through iis, slower page runs. can determine how many chunks asp.net requires page browsing page, viewing source, , saving file disk. determine number of chunks, divide page size 31.

has architecture been changed since 2.0, 3.5 , 4.0?
if whats new chunk size each of new versions of .net?

[edit]
been more 2 weeks since posting still no correct reply :(
, please not provide speculative answers

i think real question - matter? original article horribly written make think does. 31kb chunks returned worker process iis on 1 system, did not mean 31kb chunks returned client. iis processes chunks separately determines how chunk them send client. performance not related # of chunks, it's related # of bytes.

changing size of chunks not change performance in appreciable way. trying change internal memory page size on word document. think reason ms hasn't mentioned chunk size since 2004 - it's internal measure has no appreciable bearing on performance.


Comments

Popular posts from this blog

c++ - Convert big endian to little endian when reading from a binary file -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

unicode - Are email addresses allowed to contain non-alphanumeric characters? -