CHUNKED transfer data is prohibited in Jetty

Slow transfers in Jetty with chunked transfer encoding at certain buffer size

It seems that to get good performance with Jetty, you must either:

  • When callingsetContentLength (no chunked transfer encoding) and use a buffer for writethat’s the same size as the response buffer size.
  • When using chunked transfer encoding, use a write buffer that’s at least 12 bytes smaller than the response buffer size, and callflush After each write.

It is verified that there is no problem, but non-chunked performance consumes a lot on the server side.

Quotation: http://stackoverflow.com/questions/9031311/slow-transfers-in-jetty-with-chunked-transfer-encoding-at-certain-buffer- size

Slow transfers in Jetty with chunked transfer encoding at certain buffer size

It seems that to get good performance with Jetty, you must either:

  • When callingsetContentLength (no chunked transfer encoding) and use a buffer for writethat’s the same size as the response buffer size.
  • When using chunked transfer encoding, use a write buffer that’s at least 12 bytes smaller than the response buffer size, and callflush after each write.

It has been verified that there is no problem, but no Chunked consumes a lot of performance on the server side.

Quotation: http://stackoverflow.com/questions/9031311/slow-transfers-in-jetty-with-chunked-transfer-encoding-at-certain-buffer- size

Leave a Comment

Your email address will not be published.