Hi Luke, I have not hit a limit yet and the current implementation using a pool of TCP connections works fine.
I considered this after taking a look at the RethinkDB Elixir client, which uses multiplexing. RabbitMQ, another component in my infra-structure allows up to 65536 logic channels in a single TCP Connection. I'm using same Riak cluster as a persistence layer to several small apps, and each apps keeps a pool of TCP connection spread across all nodes in the cluster. I'm just considering the options to keep the file handle count lower on the server side. Regards, Paulo On Thu, Dec 31, 2015 at 5:21 PM, Luke Bakken <lbak...@basho.com> wrote: > Hi Paulo, > > Why are you considering this? Are you running into issues or > limitations using the current Erlang client? > > -- > Luke Bakken > Engineer > lbak...@basho.com > > On Thu, Dec 31, 2015 at 12:47 AM, Paulo Almeida > <paulo.m.m.alme...@gmail.com> wrote: > > > > Hi, > > > > A poolboy or other connection pool based solution still means 1 open tcp > connection per worker. I'm exploring the option of having a single TCP > connection (actually 1 for each Riak node) and then multiplex concurrent > requests to a DB node in a single TCP connection (think HTTP/2 TCP > connection multiplexing). > > > > Thanks. > > > > Paulo >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
