Context Navigation

Changes between Initial Version and Version 1 of Ticket #33497, comment 44

initial	v1
2	2	> This make sense, a small timeout value increases the chance to see this error if you are already running out of connections.
3	3
4		My mistake, I meant to say "large timeout value". My containers each answer ~2 requests per second, average response time is about 400ms. It shouldn't take many connections to service this workload (even one connection should work, I think), and yet, with pool timeouts set to 30s and the pool max size set to 16, I'm seeing many such errors. Which is why it seems to me that the new pooling support hasn't solved this particular problem.
	4	My mistake, I meant to say "large timeout value". My containers each answer ~2 requests per second, average response time is about 400ms. It shouldn't take many connections to service this workload (even one connection should work, I think), and yet, with pool timeouts set to 30s and the pool max size set to 16, I'm seeing many such errors when pooling is enabled. Which is why it seems to me that the new pooling support hasn't solved this particular problem.