SDK 2.0.0.1, Connection Pooling & Connection Timeouts

[jmorris]

@arkadyb

How good is this solution in terms of well crowded sites? Whould not it be better to keep 1 opened bucket per user session and close it when user leaves the site?

This should be fine. If you opened one bucket per session then you would end up using way to many connections. The client is thread safe, so it’s intended to be shared by many threads, such as in a ASP.NET environment.

@arkadyb

In case of single bucket per app solution, do i need to put max connection to some reasonable big value?

It depends upon the amount of traffic you are serving. If you start getting timed out responses on the client-side (ResponseStatus.ClientFailure), then bumping up the MaxSize should help there, maybe to 5 or 10 or even higher.