From 95b1d094c6bd1228bf95f013145942f7bf880794 Mon Sep 17 00:00:00 2001 From: Igor Lukanin Date: Sat, 13 Jan 2024 21:27:38 +0100 Subject: [PATCH] docs: Clean up --- docs/pages/product/faqs/general.mdx | 19 ------------------- 1 file changed, 19 deletions(-) diff --git a/docs/pages/product/faqs/general.mdx b/docs/pages/product/faqs/general.mdx index 7e79bd10e1eb0..b0dc22f385340 100644 --- a/docs/pages/product/faqs/general.mdx +++ b/docs/pages/product/faqs/general.mdx @@ -19,22 +19,3 @@ Yes. Cube Cloud provides free and a set of [paid tiers](https://cube.dev/pricing). Each tier comes with additional features, however, you're welcome to use development instances indefinitely if they satisfy your needs. - -## What is the difference between CUBEJS_CONCURRENCY and CUBEJS_DB_MAX_POOL? - -`CUBEJS_CONCURRENCY` specifies the maximum number of queries that can be -executed concurrently on your source database. This variable should reflect the -limitations of your database, and will help limit the number of queries that are -sent from cube. - -`CUBEJS_DB_MAX_POOL` allows you to set a maximum number of connection pools to -your database. This only applies to databases that use connection pooling -(Postgresql, Redshift, Clickhouse) and is not applicable to databases without it -(BigQuery, Snowflake). The concurrency limit specified in `CUBEJS_CONCURRENCY` -will supersede the number of connections if it is lower. - -For example, if your database has a hard concurrency limit of 10 that cannot be -changed, but you wish to raise the concurrency limit to 50 you would first set -`CUBEJS_CONCURRENCY=50` and `CUBEJS_DB_MAX_POOL=5` or higher. Note that some -data warehouses (BigQuery, Snowflake) do not use connection pooling so this -parameter is not applicable.