4

I am creating a reverse proxy and I am trying to find the optimal buffer for a response size for a chunked transfer-encoding. Currently I have it set at 4 kb. Is this number OK, or is there a better size that I should be using. I would like this backed up with some tests if at all possible.

I would also accept a property setting somebody knows about in the .NET framework that has a default value.

sjakobi
  • 3,546
  • 1
  • 25
  • 43
Nick Berardi
  • 54,393
  • 15
  • 113
  • 135

2 Answers2

3

The optimal size is going to be rather application and network specific. There was a previous post that offered suggestions on measuring the best chunk size given the environment.

J2ME used to default to 2KB chunks (that's client-to-server). But I have no idea what .NET defaults to. Unfortunately the HTTP Spec on chunking offers no guidance either.

Community
  • 1
  • 1
DavGarcia
  • 18,540
  • 14
  • 58
  • 96
1

I had large file transfers that were killing the web server so I implemented chunking per this article: http://support.microsoft.com/kb/812406

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

Cole
  • 742
  • 2
  • 7
  • 14
  • Setting it to 200K did increase the speed of the transfer to what it was previously without chunking – Cole Jun 29 '10 at 23:48