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 calling
setContentLength
(no chunked transfer encoding) and use a buffer forwrite
that’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 call
flush
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 calling
setContentLength
(no chunked transfer encoding) and use a buffer forwrite
that’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 call
flush
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