From b8a6366d1ae6ff69e2c6bb030d49b8bd442af769 Mon Sep 17 00:00:00 2001 From: Tyler Renelle Date: Thu, 13 Mar 2014 11:19:22 -0600 Subject: [PATCH] Revert "chore(cluster): set max #cores to 1 for now (we're maxing memory again)" This reverts commit 3f5221755c21ea7dfbc0278218560463300eacc1. --- src/server.js | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/server.js b/src/server.js index 02664c94a3..bef7642207 100644 --- a/src/server.js +++ b/src/server.js @@ -8,11 +8,9 @@ var logging = require('./logging'); var isProd = nconf.get('NODE_ENV') === 'production'; var isDev = nconf.get('NODE_ENV') === 'development'; -// The max num of CPUs to enable with cluster. On heroku, our app is pretty beefy in memory, so we're knocking back to 1 -var MAX_CORES = 1; if (cluster.isMaster && (isDev || isProd)) { // Fork workers. - _.times(_.min([require('os').cpus().length,MAX_CORES]), function(){ + _.times(_.min([require('os').cpus().length,2]), function(){ cluster.fork(); });