Re: Re: Concurrency - Multiple database connections

Re: Concurrency - Multiple database connections

As a long time redis user, the speeds or nodejs and redis are approx
the following
on a single 3.0 Ghz Core
1.) redis (for SET/GET) 110K-120K/s
2.) nodejs (for hello-world) 12K/s
               (for a page w/ a single redis INCR) 10K/s

I have been using mranneys node_redis client: http://github.com/mranney/node_redis
(which works w/ node 0.3)
and have been benchmarking nodejs+redis against php+mysql in the redis
dev-group: http://bit.ly/ba2ANx (its an ongoing benchmark)

So you need 10 nodejs cores against 1 redis core to saturate redis
(which is a good ratio because redis does not yet have a cluster:)

On Oct 14, 5:50 am, rtweed <rob.tw...@...> wrote:
> Thanks guys!
>
> On 14 Oct, 13:21, Tim Smart <t...@...> wrote:
>
>
>
> > Redis doesn't need multiple sockets really, as it pipelines requests. (If
> > that was the database you were thinking about using)
>
> > Tim.
>
> > On 15 October 2010 00:48, Arnout Kazemier <i...@...> wrote:
>
> > > Here is something I use in my node-memcached driver;
>
> > >http://github.com/3rd-Eden/node-memcached/blob/master/lib/connection....
>
> > > implementation;
> > >http://github.com/3rd-Eden/node-memcached/blob/master/nMemcached.js#L...
>
> > > or:
> > >http://github.com/mrohad/Alligator/blob/79ee8a15d1b50125699c774bb55d2...
>
> > > On Oct 14, 2010, at 1:23 PM, rtweed wrote:
>
> > > > Yes I understand that and that's what I'm asking - how to create a
> > > > connection pool.  Which modules....and any examples of anyone using
> > > > them with, eg Redis?
>
> > > > On 14 Oct, 12:03, Arnout Kazemier <i...@...> wrote:
> > > >> Threads and multiple sockets are different things. If you want to
> > > connect to your database over multiple sockets, i suggest you create a
> > > connection pool.
> > > >> There are already a couple of modules that do this for you. Which should
> > > make it fairly easy to implement.
>
> > > >> On Oct 14, 2010, at 1:00 PM, rtweed wrote:
>
> > > >>> I may just not have found what I'm looking for, but I haven't found
> > > >>> any readily available mechanism in the Node.js ecosystem for
> > > >>> distributing the load on a back-end database/store (eg Redis) across
> > > >>> multiple TCP sockets.  For example, I've only ever seen examples on
> > > >>> how to use fictorial's redis-node-client with a single socket.  I know
> > > >>> Redis is fast, but there must come a point when it (or some other
> > > >>> database connected in a similar way) just won't be able to keep up
> > > >>> with the queue of requests on the Node.js side via a single socket
> > > >>> connection.
>
> > > >>> So I'd be interested to know what work is being/has been done on TCP
> > > >>> socket pooling within Node.js to allow database load to be spread
> > > >>> across several threads.  Perhaps there's some examples I've missed?
>
> > > >>> [Of course databases with an HTTP interface aren't a problem since the
> > > >>> HTTP layer can do this work for me - so I'm thinking of simple TCP
> > > >>> socket interfaced databases, Redis being a good example of the genre]
>
> > > >>> Many thanks!
>
> > > >>> --
> > > >>> You received this message because you are subscribed to the Google
> > > Groups "nodejs" group.
> > > >>> To post to this group, send email to nodejs@...
> > > >>> To unsubscribe from this group, send email to
> > > nodejs+unsubscribe@...<nodejs%2Bunsubscribe <at> googlegroups.com>
> > > .
> > > >>> For more options, visit this group athttp://
> > > groups.google.com/group/nodejs?hl=en.
>
> > > > --
> > > > You received this message because you are subscribed to the Google Groups
> > > "nodejs" group.
> > > > To post to this group, send email to nodejs@...
> > > > To unsubscribe from this group, send email to
> > > nodejs+unsubscribe@...<nodejs%2Bunsubscribe <at> googlegroups.com>
> > > .
> > > > For more options, visit this group at
> > >http://groups.google.com/group/nodejs?hl=en.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "nodejs" group.
> > > To post to this group, send email to nodejs@...
> > > To unsubscribe from this group, send email to
> > > nodejs+unsubscribe@...<nodejs%2Bunsubscribe <at> googlegroups.com>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/nodejs?hl=en.

--

-- 
You received this message because you are subscribed to the Google Groups "nodejs" group.
To post to this group, send email to nodejs@...
To unsubscribe from this group, send email to nodejs+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nodejs?hl=en.