sync router docs: 2024-06-03T02:19:17Z

Author: github-actions

module/router/.gitbook/assets/pyfunc_ensembler_config.png

@@ -47,6 +47,11 @@ Configure the resources required for the enricher. There are 3 required inputs,
 
 **Min/Max Replicas**: Min/max number of replicas for your enricher. Scaling of the enricher based on traffic volume will be automatically done for you.
 
+**CPU Limit**: By default, Turing determines the CPU limits of all deployed components using platform-level configured
+values. These CPU limits is calculated as a factor of the user-defined CPU request value for each component (e.g. 2x
+of the CPU request value). However, you can override this platform-level configured value by setting this value
+explicitly on the UI (as seen above) or via the SDK.
+
 Optionally, modify the autoscaling policy on the enricher.
 
 ![](../../.gitbook/assets/autoscaling_policy_panel.png)

module/router/.gitbook/assets/resources_panel.png

@@ -83,6 +83,11 @@ Configure the resources required for the ensembler. There are 3 required inputs,
 
 **Min/Max Replicas**: Min/max number of replicas for your ensembler. Scaling of the ensembler based on traffic volume will be automatically done for you.
 
+**CPU Limit**: By default, Turing determines the CPU limits of all deployed components using platform-level configured 
+values. These CPU limits is calculated as a factor of the user-defined CPU request value for each component (e.g. 2x 
+of the CPU request value). However, you can override this platform-level configured value by setting this value 
+explicitly on the UI (as seen above) or via the SDK.
+
 Optionally, modify the autoscaling policy on the ensembler.
 
 ![](../../.gitbook/assets/autoscaling_policy_panel.png)
@@ -125,6 +130,11 @@ registered in your current project. You'll also need to indicate your desired ti
 
 **Min/Max Replicas**: Min/max number of replicas for your ensembler. Scaling of the ensembler based on traffic volume will be automatically done for you.
 
+**CPU Limit**: By default, Turing determines the CPU limits of all deployed components using platform-level configured
+values. These CPU limits is calculated as a factor of the user-defined CPU request value for each component (e.g. 2x
+of the CPU request value). However, you can override this platform-level configured value by setting this value
+explicitly on the UI (as seen above) or via the SDK.
+
 Optionally, modify the autoscaling policy on the ensembler.
 
 ![](../../.gitbook/assets/autoscaling_policy_panel.png)