tuning riak for 100s of concurrent connections

Wilson MacGyver wmacgyver at gmail.com
Fri Feb 25 13:31:12 EST 2011

Another possibility that comes to mind to avoid the setup cost is to
do connection pool
of some sorts.

Does any of the riak client lib supports connection pooling?

On Fri, Feb 25, 2011 at 1:25 PM, Sean Cribbs <sean at basho.com> wrote:
> Now you're talking about tweaking kernel-level settings -- something well outside my expertise (although TCP slow-start comes to mind).  That said, it's kind of hard not to use TCP if you want a reliable connection, warts and all.
> Sean Cribbs <sean at basho.com>
> Developer Advocate
> Basho Technologies, Inc.
> http://basho.com/
> On Feb 25, 2011, at 1:06 PM, Wilson MacGyver wrote:
>> any advise to solve this?
>> On Fri, Feb 25, 2011 at 1:05 PM, Sean Cribbs <sean at basho.com> wrote:
>>> Yes, the majority of the cost is probably in TCP setup. That pain is happening at the TCP stack level, not in Erlang.  It's actually really cheap and easy to spawn a new process in Erlang, so there's no reason to have "standby workers", especially when they don't need to maintain state between requests.

Omnem crede diem tibi diluxisse supremum.

More information about the riak-users mailing list