From bf20419b708fa3115703192eda0b866bc787d429 Mon Sep 17 00:00:00 2001 From: prha Date: Thu, 19 Dec 2024 10:24:44 -0800 Subject: [PATCH 1/2] add deployment settings pointer for concurrency docs --- docs/content/guides/limiting-concurrency-in-data-pipelines.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx b/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx index ab45e8b7e61e1..89162fac96199 100644 --- a/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx +++ b/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx @@ -422,7 +422,7 @@ The concurrency key should match the name that the op/asset is tagged with. For A default concurrency limit can be configured for the instance, for any concurrency keys that do not have an explicit limit set: -- **Dagster+**: Use the [Dagster+ UI or the `dagster-cloud` CLI][cloud-deployment-settings] +- **Dagster+**: Use the deployment settings via the [Dagster+ UI or the `dagster-cloud` CLI][cloud-deployment-settings] - **Dagster Open Source**: Use your instance's `dagster.yaml` To enable this default value, use `concurrency.default_op_concurrency_limit`. For example, the following would set the default concurrency value for the deployment to 1: From 913170e16af2d953e8dc366c5419c0f1bbc018a9 Mon Sep 17 00:00:00 2001 From: prha Date: Thu, 19 Dec 2024 11:46:22 -0800 Subject: [PATCH 2/2] edit --- .../content/guides/limiting-concurrency-in-data-pipelines.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx b/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx index 89162fac96199..6f97af98978a9 100644 --- a/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx +++ b/docs/content/guides/limiting-concurrency-in-data-pipelines.mdx @@ -422,8 +422,8 @@ The concurrency key should match the name that the op/asset is tagged with. For A default concurrency limit can be configured for the instance, for any concurrency keys that do not have an explicit limit set: -- **Dagster+**: Use the deployment settings via the [Dagster+ UI or the `dagster-cloud` CLI][cloud-deployment-settings] -- **Dagster Open Source**: Use your instance's `dagster.yaml` +- **Dagster+**: Edit the `concurrency` config in deployment settings via the [Dagster+ UI or the `dagster-cloud` CLI][cloud-deployment-settings] +- **Dagster Open Source**: Edit the `concurrency` config in your instance's `dagster.yaml` To enable this default value, use `concurrency.default_op_concurrency_limit`. For example, the following would set the default concurrency value for the deployment to 1: