Hi,
I don't know how practical this would be but could pound reuse a
connection (if available) after randomly selecting a backend? By maintaining
a connection pool for each backend I would have thought the number of TCP
connections being created/destroyed between pound and the backends would
be significantly reduced. Particularly if the backends were configured
with a large keep alive period to take advantage of this.
This would preserve the random distribution of client requests over the
backend servers whilst also getting the benefits of reusing connections.
The only problem I can see would be the overhead/complexity of maintaining
the connection pools.
Regards,
Andrew
On Mon, 22 Sep 2008, Robert Segall wrote:
We'll look at the possibility of optimising this for randomly assigned
back-ends. In the meantime (for all list members): how many people could
benefit from it?
--
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
