What is the optimal response size for packet transmission in ASP.NET?

I am creating a reverse proxy and I am trying to find the optimal buffer for the response size for chunked transfer-encoding. I am currently setting it to 4 kb. Is this number OK, or is there the best size I should use. I would like this to be supported by some tests, if at all possible.

I also agree with the property setting that someone knows about in the .NET Framework, which has a default value.

+4
source share
2 answers

The optimal size will be more specific to the application and the network. There was a previous post suggesting how to measure the maximum size of a piece, given the environment.

J2ME is used by default for 2K blocks (this client server). But I have no idea what .NET is by default. Unfortunately, the HTTP Spec on chunking also offers no guidance.

+3
source

I had large file transfers that killed the web server, so I implemented chunking for this article: http://support.microsoft.com/kb/812406

Customers immediately complained that downloading files took 3 times, the buffer was set to 10K. In some cases, these files are 80-100 MB in size. I raised the buffer to 200K and will post my results.

0
source

All Articles