From 544c9fbaf7d5203b7f39d9c44c017c0bf6302b8a Mon Sep 17 00:00:00 2001
From: Marti Martz <Martii@users.noreply.github.com>
Date: Tue, 18 Dec 2018 19:39:00 -0700
Subject: [PATCH] Increase `poolSize` depending on multiplier (#1552)

* This didn't seem to help in a direct test on production but doing since it's the logical thing to do with our current process manager.

NOTE(S):
* We don't currently have clustering management in the project itself but may at some point in the future so this could eventually use some improvement. Trying to keep this simple at start for everyone.
* Go back to the original multiplier
* This value is per thread otherwise it would be huge in each thread. Durr.
* Try triple multiplier
* Since commit notes said it didn't seem to help let's try tripling the multiplier

Applies to #1548
---
 app.js | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/app.js b/app.js
index d9fb46a01..9801b20e3 100755
--- a/app.js
+++ b/app.js
@@ -66,14 +66,15 @@ var _ = require('underscore');
 var findSessionData = require('./libs/modifySessions').findSessionData;
 
 var dbOptions = {};
+var defaultPoolSize = 5;
 if (isPro) {
   dbOptions = {
     secondaryAcceptableLatencyMS: 15,
-    poolSize: 5
+    poolSize: defaultPoolSize * 3
   }
 } else {
   dbOptions = {
-    poolSize: 5,
+    poolSize: defaultPoolSize,
     reconnectTries: 30,
     reconnectInterval: 1000
   }