From a07acb6ea83eb21b741567a64f64bdcfa275f913 Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Mon, 26 Aug 2024 12:55:02 -0600 Subject: [PATCH 01/12] update naming to query performance factor --- ...-search.md => query-performance-factor.md} | 46 +++++++++---------- 1 file changed, 23 insertions(+), 23 deletions(-) rename content/operate/oss_and_stack/stack-with-enterprise/search/{scalable-search.md => query-performance-factor.md} (68%) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/scalable-search.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md similarity index 68% rename from content/operate/oss_and_stack/stack-with-enterprise/search/scalable-search.md rename to content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index f48457cfdf..3905fdc66e 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/scalable-search.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -1,17 +1,17 @@ --- -Title: Enable scalable Redis Query Engine in Redis Enterprise +Title: Enable Query Performance Factor For Redis Query Engine in Redis Enterprise alwaysopen: false categories: - docs - operate - stack -description: Enable the scalable Redis Query Engine in Redis Enterprise to increase the performance of queries. +description: Enable the Query performance factor for Redis Query Engine in Redis Enterprise to increase the performance of queries. linkTitle: Enable scalable Redis Query Engine weight: 20 -aliases: /operate/oss_and_stack/stack-with-enterprise/search/scalable-search/ +aliases: /operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor/ --- -Redis Query Engine is a capability intended to increase the performance of queries, including [vector search]({{}}). When enabled, it allows you to increase a database's compute capacity and throughput by allocating more virtual CPUs per shard in addition to horizontal scaling with more shards. This document describes how to configure the Redis Query Engine. +Query performance factor is a capability intended to increase the performance of queries, including [vector search]({{}}). When enabled, it allows you to increase a database's compute capacity and throughput by allocating more virtual CPUs per shard in addition to horizontal scaling with more shards. This document describes how to configure the Query performance factor. {{}} Some use cases might not scale effectively. Redis experts can help determine if vertical scaling with the Redis Query Engine will boost performance for your use case and guide you on whether to use vertical scaling, horizontal scaling, or both. @@ -31,13 +31,13 @@ If you do not have a cluster that supports Redis Query Engine, [install Redis En 1. Calculate the RAM requirements using the [Index Size Calculator](https://redis.io/redisearch-sizing-calculator/). The total RAM required is the sum of the dataset and index sizes. -1. [Determine the scaling factor](#calculate-scaling-factor) you want and the required number of CPUs. Unused CPUs, above the 20% necessary for Redis, can be used for the scalable Redis Query Engine. +1. [Determine the Query performanc factor](#calculate-performance-factor) you want and the required number of CPUs. Unused CPUs, above the 20% necessary for Redis, can be used for the scalable Redis Query Engine. -1. Create a new Redis database with the number of CPUs configured for the scalable Redis Query Engine. +1. Create a new Redis database with the number of CPUs configured for the Query performance factor. -## Calculate scaling factor +## Calculate performance factor -### CPUs for Redis Query Engine +### CPUs for Query performance factor Vertical scaling of the Redis Query Engine is achieved by provisioning additional CPUs for the search module. At least 20% of the available CPUs must be reserved for Redis internal processing. Use the following formula to define the maximum number of CPUs that can be allocated to search. @@ -47,9 +47,9 @@ Vertical scaling of the Redis Query Engine is achieved by provisioning additiona | Redis internals | 20% | | Available CPUs for Redis Query Engine | floor(0.8 * x) | -### Scale factor versus CPUs +### Query performance factor versus CPUs -The following table shows the number of CPUs required for each scale factor. This calculation is sensitive to how the search index and queries are defined. Certain scenarios might yield less throughput than the ratios in the following table. +The following table shows the number of CPUs required for each performance factor. This calculation is sensitive to how the search index and queries are defined. Certain scenarios might yield less throughput than the ratios in the following table. | Scale factor | Minimum CPUs required for Redis Query Engine | |----------------|-----------------------------------------| @@ -63,7 +63,7 @@ The following table shows the number of CPUs required for each scale factor. Thi | 14 | 21 | | 16 | 24 | -### Example scale factor calculation +### Example performance factor calculation | Variable | Value | |----------|-------| @@ -72,13 +72,13 @@ The following table shows the number of CPUs required for each scale factor. Thi | Scale factor | 4x | | Minimum CPUs required for scale factor | 6 | -## Enable scalable Redis Query Engine +## Enable Query performance factor -To enable the scalable Redis Query Engine in Redis Enterprise, use the [REST API]({{}}) to create a new database or update an existing database. +To enable the performance factor in Redis Enterprise, use the [REST API]({{}}) to create a new database or update an existing database. ### Create new database -To create a database with the scalable Redis Query Engine enabled, use the [create database REST API endpoint]({{}}) with a [BDB object]({{}}) that includes the following parameters: +To create a database with the Query performance factor enabled, use the [create database REST API endpoint]({{}}) with a [BDB object]({{}}) that includes the following parameters: ```json { @@ -91,11 +91,11 @@ To create a database with the scalable Redis Query Engine enabled, use the [crea } ``` -See [Calculate scaling factor](#calculate-scaling-factor) to determine the value to use for ``. +See [Calculate performance factor](#calculate-performance-factor) to determine the value to use for ``. #### Example REST API request for a new database -The following JSON is an example request body used to create a new database with the scalable Redis Query Engine enabled: +The following JSON is an example request body used to create a new database with a 4x Query performance factor enabled: ```json { @@ -127,18 +127,18 @@ curl -k -u ":" https://:9443/v1/bdbs -H "Content-Type:appl ### Update existing database -To enable the scalable Redis Query Engine for an existing database, use the following REST API requests: +To enable the Query performance factor for an existing database, use the following REST API requests: - [Update database configuration]({{}}) to modify the DMC proxy. -- [Upgrade module]({{}}) to set the search module’s scaling factor. +- [Upgrade module]({{}}) to set the search module’s Query performance factor. {{}} - Because this procedure also restarts the database shards, you should perform it during a maintenance period. - This procedure overwrites any existing module configuration parameters. {{}} -The following example script uses both endpoints to configure a 4x scale factor: +The following example script uses both endpoints to configure a 4x Query performance factor: ```sh #!/bin/bash @@ -167,7 +167,7 @@ curl -o /dev/null -s -k -u ":" https://:9443/v1/bdbs/$DB_I ## Monitoring Redis Query Engine -To monitor a database with the scalable Redis Query Engine enabled: +To monitor a database with a Query performance factor enabled: 1. Integrate your Redis Enterprise deployment with Prometheus. See [Prometheus and Grafana with Redis Enterprise]({{}}) for instructions. @@ -175,10 +175,10 @@ To monitor a database with the scalable Redis Query Engine enabled: The following Prometheus UI screenshot shows `redis_process_cpu_usage_percent` spikes for a database with two shards: - - 1st 100% spike: [`memtier_benchmark`](https://github.com/RedisLabs/memtier_benchmark) search test at the default scale factor (1 CPU per shard for search). + - 1st 100% spike: [`memtier_benchmark`](https://github.com/RedisLabs/memtier_benchmark) search test at the default (no additional CPUs for search). - - 2nd 100% spike: reconfiguration and shard restart for a 4x scale factor. + - 2nd 100% spike: reconfiguration and shard restart for a 4x Query performance factor. - - 3rd 600% spike: `memtier_benchmark` search test with threading at a 4x scale factor (6 CPUs per shard). + - 3rd 600% spike: `memtier_benchmark` search test with threading at a 4x Query performance factor (6 CPUs per shard). {{The Prometheus graph shows three spikes for redis_process_cpu_usage_percent: 100%, another 100%, then 600%.}} From 7aadf61e96e03002f038fe82f3b9ea44554b9e7e Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:15:05 -0600 Subject: [PATCH 02/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 3905fdc66e..7d785469cf 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -1,5 +1,5 @@ --- -Title: Enable Query Performance Factor For Redis Query Engine in Redis Enterprise +Title: Configure the query performance factor for Redis Query Engine in Redis Enterprise alwaysopen: false categories: - docs From 20c9d2983fff49241162092caae808731cc56622 Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:15:19 -0600 Subject: [PATCH 03/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 7d785469cf..bf38d1796d 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -8,7 +8,8 @@ categories: description: Enable the Query performance factor for Redis Query Engine in Redis Enterprise to increase the performance of queries. linkTitle: Enable scalable Redis Query Engine weight: 20 -aliases: /operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor/ +aliases: /operate/oss_and_stack/stack-with-enterprise/search/scalable-search/ + /operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor/ --- Query performance factor is a capability intended to increase the performance of queries, including [vector search]({{}}). When enabled, it allows you to increase a database's compute capacity and throughput by allocating more virtual CPUs per shard in addition to horizontal scaling with more shards. This document describes how to configure the Query performance factor. From 1bfbd2c2929979b90984463a0c1fd2590d97523d Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:15:41 -0600 Subject: [PATCH 04/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index bf38d1796d..186e4cdfc2 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -6,7 +6,7 @@ categories: - operate - stack description: Enable the Query performance factor for Redis Query Engine in Redis Enterprise to increase the performance of queries. -linkTitle: Enable scalable Redis Query Engine +linkTitle: Configure query performance factor weight: 20 aliases: /operate/oss_and_stack/stack-with-enterprise/search/scalable-search/ /operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor/ From 2b8d2cc6b2047a2662005be000900808c9344694 Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:15:57 -0600 Subject: [PATCH 05/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 186e4cdfc2..1b3fcfb326 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -12,7 +12,7 @@ aliases: /operate/oss_and_stack/stack-with-enterprise/search/scalable-search/ /operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor/ --- -Query performance factor is a capability intended to increase the performance of queries, including [vector search]({{}}). When enabled, it allows you to increase a database's compute capacity and throughput by allocating more virtual CPUs per shard in addition to horizontal scaling with more shards. This document describes how to configure the Query performance factor. +Query performance factors are intended to increase the performance of queries, including [vector search]({{}}). When enabled, it allows you to increase a database's compute capacity and throughput by allocating more virtual CPUs per shard in addition to horizontal scaling with more shards. This document describes how to configure the query performance factor. {{}} Some use cases might not scale effectively. Redis experts can help determine if vertical scaling with the Redis Query Engine will boost performance for your use case and guide you on whether to use vertical scaling, horizontal scaling, or both. From 87a61c83c98f2da5897d9c2506d6300e20984faf Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:16:14 -0600 Subject: [PATCH 06/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 1b3fcfb326..9818764f0b 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -139,7 +139,7 @@ To enable the Query performance factor for an existing database, use the followi - This procedure overwrites any existing module configuration parameters. {{}} -The following example script uses both endpoints to configure a 4x Query performance factor: +The following example script uses both endpoints to configure a 4x query performance factor: ```sh #!/bin/bash From 6b25c85ca50a908ea32d94281196872b638ccd4c Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:16:23 -0600 Subject: [PATCH 07/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 9818764f0b..afb5f6a559 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -178,7 +178,7 @@ To monitor a database with a Query performance factor enabled: - 1st 100% spike: [`memtier_benchmark`](https://github.com/RedisLabs/memtier_benchmark) search test at the default (no additional CPUs for search). - - 2nd 100% spike: reconfiguration and shard restart for a 4x Query performance factor. + - 2nd 100% spike: reconfiguration and shard restart for a 4x query performance factor. - 3rd 600% spike: `memtier_benchmark` search test with threading at a 4x Query performance factor (6 CPUs per shard). From 1c1fdb3e01030ee806e20cc657af4f7ca7c1df8d Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:16:47 -0600 Subject: [PATCH 08/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index afb5f6a559..0acfb5c27c 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -5,7 +5,7 @@ categories: - docs - operate - stack -description: Enable the Query performance factor for Redis Query Engine in Redis Enterprise to increase the performance of queries. +description: Configure the query performance factor for Redis Query Engine in Redis Enterprise to increase the performance of queries. linkTitle: Configure query performance factor weight: 20 aliases: /operate/oss_and_stack/stack-with-enterprise/search/scalable-search/ From a189f29ab650f90abf64448995a2bf599ea8a332 Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:17:03 -0600 Subject: [PATCH 09/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 0acfb5c27c..5ad40bd757 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -132,7 +132,7 @@ To enable the Query performance factor for an existing database, use the followi - [Update database configuration]({{}}) to modify the DMC proxy. -- [Upgrade module]({{}}) to set the search module’s Query performance factor. +- [Upgrade module]({{}}) to set the search module’s query performance factor. {{}} - Because this procedure also restarts the database shards, you should perform it during a maintenance period. From 54291a8e63b6157ce1a12be953c202aef282fa55 Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:17:12 -0600 Subject: [PATCH 10/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 5ad40bd757..fe52c1488e 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -168,7 +168,7 @@ curl -o /dev/null -s -k -u ":" https://:9443/v1/bdbs/$DB_I ## Monitoring Redis Query Engine -To monitor a database with a Query performance factor enabled: +To monitor a database with a query performance factor configured: 1. Integrate your Redis Enterprise deployment with Prometheus. See [Prometheus and Grafana with Redis Enterprise]({{}}) for instructions. From 4bf23f91ef9e69338e495a0ec6f688899a26efca Mon Sep 17 00:00:00 2001 From: Joey Whelan Date: Tue, 27 Aug 2024 08:17:27 -0600 Subject: [PATCH 11/12] Update content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md Co-authored-by: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> --- .../stack-with-enterprise/search/query-performance-factor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index fe52c1488e..6222e8ce3d 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -180,6 +180,6 @@ To monitor a database with a query performance factor configured: - 2nd 100% spike: reconfiguration and shard restart for a 4x query performance factor. - - 3rd 600% spike: `memtier_benchmark` search test with threading at a 4x Query performance factor (6 CPUs per shard). + - 3rd 600% spike: `memtier_benchmark` search test with threading at a 4x query performance factor (6 CPUs per shard). {{The Prometheus graph shows three spikes for redis_process_cpu_usage_percent: 100%, another 100%, then 600%.}} From 512e4169a2538b6d2222b752b4fa704c98d70bce Mon Sep 17 00:00:00 2001 From: Rachel Elledge <86307637+rrelledge@users.noreply.github.com> Date: Tue, 27 Aug 2024 14:44:00 -0500 Subject: [PATCH 12/12] Apply remaining suggestions from code review --- .../search/query-performance-factor.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md index 6222e8ce3d..2dced5729a 100644 --- a/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md +++ b/content/operate/oss_and_stack/stack-with-enterprise/search/query-performance-factor.md @@ -32,13 +32,13 @@ If you do not have a cluster that supports Redis Query Engine, [install Redis En 1. Calculate the RAM requirements using the [Index Size Calculator](https://redis.io/redisearch-sizing-calculator/). The total RAM required is the sum of the dataset and index sizes. -1. [Determine the Query performanc factor](#calculate-performance-factor) you want and the required number of CPUs. Unused CPUs, above the 20% necessary for Redis, can be used for the scalable Redis Query Engine. +1. [Determine the query performance factor](#calculate-performance-factor) you want and the required number of CPUs. Unused CPUs, above the 20% necessary for Redis, can be used for the scalable Redis Query Engine. 1. Create a new Redis database with the number of CPUs configured for the Query performance factor. ## Calculate performance factor -### CPUs for Query performance factor +### CPUs for query performance factor Vertical scaling of the Redis Query Engine is achieved by provisioning additional CPUs for the search module. At least 20% of the available CPUs must be reserved for Redis internal processing. Use the following formula to define the maximum number of CPUs that can be allocated to search. @@ -73,13 +73,13 @@ The following table shows the number of CPUs required for each performance facto | Scale factor | 4x | | Minimum CPUs required for scale factor | 6 | -## Enable Query performance factor +## Configure query performance factor -To enable the performance factor in Redis Enterprise, use the [REST API]({{}}) to create a new database or update an existing database. +To configure the query performance factor in Redis Enterprise, use the [REST API]({{}}) to create a new database or update an existing database. ### Create new database -To create a database with the Query performance factor enabled, use the [create database REST API endpoint]({{}}) with a [BDB object]({{}}) that includes the following parameters: +To create a database and configure the query performance factor, use the [create database REST API endpoint]({{}}) with a [BDB object]({{}}) that includes the following parameters: ```json { @@ -96,7 +96,7 @@ See [Calculate performance factor](#calculate-performance-factor) to determine t #### Example REST API request for a new database -The following JSON is an example request body used to create a new database with a 4x Query performance factor enabled: +The following JSON is an example request body used to create a new database with a 4x query performance factor configured: ```json { @@ -128,7 +128,7 @@ curl -k -u ":" https://:9443/v1/bdbs -H "Content-Type:appl ### Update existing database -To enable the Query performance factor for an existing database, use the following REST API requests: +To configure the query performance factor for an existing database, use the following REST API requests: - [Update database configuration]({{}}) to modify the DMC proxy.