Databases
StackOverflow2013
Postsdbo
PONode.js, multi-threading and Socket.io
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONode.js, multi-threading and Socket.io
    primarykey
    data
    text
    <p>I'm looking to get Socket.io to work multi-threaded with <a href="http://nodejs.org/docs/latest/api/cluster.html" rel="noreferrer">native load balancing</a> ("cluster") in Node.js v.0.6.0 and later.</p> <p>From what I understand, Socket.io uses Redis to store its internal data. My understanding is this: instead of spawning a new Redis instance for every worker, we want to force the workers to use the same Redis instance as the master. Thus, connection data would be shared across all workers.</p> <p>Something like this in the master:</p> <pre><code>RedisInstance = new io.RedisStore; </code></pre> <p>The we must somehow pass <code>RedisInstance</code> to the workers and do the following:</p> <pre><code>io.set('store', RedisInstance); </code></pre> <p>Inspired by <a href="https://github.com/3rd-Eden/nodejsconfit-2011/tree/master/cluster" rel="noreferrer">this implementation</a> using the old, 3rd party cluster module, I have the following non-working implementation:</p> <pre><code>var cluster = require('cluster'); var http = require('http'); var numCPUs = require('os').cpus().length; if (cluster.isMaster) { // Fork workers. for (var i = 0; i &lt; numCPUs; i++) { cluster.fork(); } var sio = require('socket.io') , RedisStore = sio.RedisStore , io = sio.listen(8080, options); // Somehow pass this information to the workers io.set('store', new RedisStore); } else { // Do the work here io.sockets.on('connection', function (socket) { socket.on('chat', function (data) { socket.broadcast.emit('chat', data); }) }); } </code></pre> <p>Thoughts? I might be going completely in the wrong direction, anybody can point to some ideas?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDavid Chouinard
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONode.js, multi-threading and Socket.io
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONode.js, multi-threading and Socket.io
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PONode.js, multi-threading and Socket.io
      1. USRollin_s
      1. VTFavorite
    1. COI wonder what approach you end up using.
      singulars
      1. PONode.js, multi-threading and Socket.io
      1. USmvbl fst
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload