Caldarale, Charles R wrote:
From: André Warnier [mailto:a...@ice-sa.com]
Subject: Re: apache/tomcat communication issues (502 response)
That is because a KeepAlive connection will keep a server child (or
thread) tied to that particular client connection, until the KeepAlive
expires, probably doing nothing most of the time.
But think about this in the context of a modern 64-bit server environment:
what's wrong with keeping these idle thread(s) around? When process space was
at a premium, it made sense to trade off a little CPU time rebuilding
connections versus chewing up the limited address space; now that the resource
limits are essentially gone, you might as well take advantage of it.
It would be better in most cases to have the client re-build a
connection more often, and allow those server children/threads
to take care of other requests in the meantime.
An idle thread costs very little (at least in a 64-bit world) - configure more
of them.
Mere curiosity :
You seem to imply that idle threads use less resources in the 64-bit
world than (presumably) in a lesser-number-of-bit world.
Why is that ? Can you elaborate a little bit ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
