ByteEncoder and ByteDecoder allocate 8+M buffer each which means 16+M for each connection.

This means we need to increase the MaxDirectMemorySize quite significantly to be able to create a decent number of connections to perform well under many concurrent requests.

While I can understand why this has been done, it would be good to be able to at least configure the MAX_OBJECT_SIZE for our application, as we'll only ever be passing around documents < 1M.

Alternatively, could the encoder and decoder stream the requests using a much smaller buffer.

Am happy to look at creating a patch depending upon preferred solution.