From 0e99a0ddda06b30e50b25be4890b5deb59e3342e Mon Sep 17 00:00:00 2001 From: Pavel Tiunov Date: Tue, 5 May 2020 11:24:09 -0700 Subject: [PATCH] Update Deployment.md --- docs/Cube.js-Backend/Deployment.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/Cube.js-Backend/Deployment.md b/docs/Cube.js-Backend/Deployment.md index cab56cd52ca6d..1dd657be5eee8 100644 --- a/docs/Cube.js-Backend/Deployment.md +++ b/docs/Cube.js-Backend/Deployment.md @@ -35,7 +35,8 @@ If `REDIS_URL` is provided Cube.js will create Redis pool with 2 min and 1000 ma No pool behavior with each connection created on demand can be achieved with `CUBEJS_REDIS_POOL_MAX=0` setting. If your `CUBEJS_REDIS_POOL_MAX` too low you may see `TimeoutError: ResourceRequest timed out` errors. -As rule of a thumb you need to have `Queue Size * Number of Cube.js server instances * Number of tenants` concurrent connections to ensure best performance possible. +As a rule of a thumb you need to have `Queue Size * Number of tenants` concurrent connections to ensure best performance possible. +If you use clustered deployments please make sure you have enough connections for all Cube.js server instances. Lower number of connections still can work however Redis becomes performance bottleneck in this case. ### Running without Redis