Skip to content

Commit

Permalink
Increase poolSize depending on multiplier (#1552)
Browse files Browse the repository at this point in the history
* 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
  • Loading branch information
Martii authored Dec 19, 2018
1 parent b914392 commit 544c9fb
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions app.js
Original file line number Diff line number Diff line change
Expand Up @@ -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
}
Expand Down

0 comments on commit 544c9fb

Please sign in to comment.