Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Actually your code should look like this:</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(); } } else { 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); // Do the work here io.sockets.on('connection', function (socket) { socket.on('chat', function (data) { socket.broadcast.emit('chat', data); }) }); } </code></pre> <p>Another option is to open Socket.IO to listen on multiple ports and have something like HAProxy load-balance stuff. Anyway you know the most important thing: using RedisStore to scale outside a process!</p> <p>Resources:</p> <p><a href="http://nodejs.org/docs/latest/api/cluster.html" rel="nofollow noreferrer">http://nodejs.org/docs/latest/api/cluster.html</a> <br /> <a href="https://stackoverflow.com/questions/5944714/how-can-i-scale-socket-io">How can I scale socket.io?</a> <br /> <a href="https://stackoverflow.com/questions/5739357/how-to-reuse-redis-connection-in-socket-io">How to reuse redis connection in socket.io?</a> <br /> <a href="https://stackoverflow.com/questions/7972077/node-scale-socket-io-nowjs-scale-across-different-instances">Node: Scale socket.io / nowjs - scale across different instances</a> <br /> <a href="http://delicious.com/alessioaw/socket.io" rel="nofollow noreferrer">http://delicious.com/alessioaw/socket.io</a></p>
    singulars
    1. This table or related slice is empty.
    1. PONode.js, multi-threading and Socket.io
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USalessioalex
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PONode.js, multi-threading and Socket.io
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWon't that implementation create a new RedisStore for every worker? Also, what would be the advantage of using something like HAProxy? Seems like using functionality present natively in Node is better.
      singulars
      1. PO
      1. USDavid Chouinard
    2. COAdvantages of HAProxy: you would have processes on different ports, which you could monitor more carefully and restart when they die (using monit, upstart). Also yes you need to create a new RedisStore for every worker. Think that cluster is an implementation above child_process.fork(), so you basically copy the app N times (the processes share the same file descriptor as far as I know).
      singulars
      1. PO
      1. USalessioalex
    3. COI just tried your code sample, seems to not be working. When single-threading, 1500 connections runs up to 50% CPU (every worker is doing a bit more work than in the sample). Using your sample, I can't get up to 500 connections before *every* process runs up to 80-90% CPU. So clearly, something is wrong since this is worsening the situation.
      singulars
      1. PO
      1. USDavid Chouinard
 

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