Hi Remy,
can you explain why we use packetSize at AjpAprProcessor attribute
bodyMessage and responseHeaderMessage?
requestHeaderMessage = new AjpMessage(packetSize);
responseHeaderMessage = new AjpMessage(packetSize);
bodyMessage = new AjpMessage(packetSize);
We want only send 8K packets!
Other problem I see now is: That we can create a packetSize
responseHeader greater then 8K but
the Outputbuffer (SocketOutputBuffer) can only handle 8K packets.
Regards
Peter
Am 12.12.2006 um 22:49 schrieb Remy Maucherat:
Peter Rossbach wrote:
Yes, but as I configured packetSize greater then 8k, I would like
to see that ajp send those big chunks.
This will not be useful performance wise. The increased packet size
is useful for sending certificates data in the first packet of the
request, and that's about it.
Currently mod_jk 1.2.20 accept those packets, but don't send
bigger pakets then 8k ( see my separate posting).
Which is most likely useless.
More memory is not a big argument. 8k is default, and only at
spezial case user use greater packetSize. Greater
PacketSize means that you send fewer GET BODY messages. This
reduce the ajp handshake overhead.
People will need to use more than 8KB is they have a large cert
chain, but will not benefit in any way from using larger packets on
output other than using more memory. I don't understand why you are
talking about "get body" messages since your changes are for
output, not input. If you can provide data which shows a
performance gain, then this could be considered.
So -1 for your changes (it's a definitive veto in 5.5 since it is
the stable branch; I'm still against it in 6.0 unless you can prove
it provides a significant benefit).
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
