Skip to content

Commit f152415

Browse files
author
github-actions
committed
sync model docs: 2024-06-03T02:22:55Z
1 parent 1bc22cf commit f152415

3 files changed

Lines changed: 48 additions & 0 deletions

File tree

63.4 KB
Loading

module/model/user/generated/model_deployment/01_deploying_a_model_version.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -150,6 +150,30 @@ with merlin.new_model_version() as v:
150150

151151
![Autoscaling Policy](../../../images/autoscaling_policy.png)
152152

153+
## CPU Limits
154+
155+
By default, Merlin determines the CPU limits of all model deployments using platform-level configured values. These CPU
156+
limits can either be calculated as a factor of the user-defined CPU request value for each deployment (e.g. 2x of the
157+
CPU request value) or as a constant value across all deployments.
158+
159+
However, users can override this platform-level configured value by setting this value explicitly on the UI or on
160+
the SDK.
161+
162+
On the UI:
163+
164+
![CPU Limits](../../../images/override_cpu_limits.png)
165+
166+
On the SDK:
167+
168+
```python
169+
merlin.deploy(
170+
v,
171+
environment_name=some_name,
172+
resource_request=ResourceRequest(cpu_limit="2"),
173+
deployment_mode=some_deployment_mode,
174+
)
175+
```
176+
153177
## Liveness Probe
154178

155179
When deploying a model version, the model container will be built with a livenes probe by default. The liveness probe will periodically check that your model is still alive, and restart the pod automatically if it is deemed to be dead.

module/model/user/templates/model_deployment/01_deploying_a_model_version.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -150,6 +150,30 @@ with merlin.new_model_version() as v:
150150

151151
![Autoscaling Policy](../../../images/autoscaling_policy.png)
152152

153+
## CPU Limits
154+
155+
By default, Merlin determines the CPU limits of all model deployments using platform-level configured values. These CPU
156+
limits can either be calculated as a factor of the user-defined CPU request value for each deployment (e.g. 2x of the
157+
CPU request value) or as a constant value across all deployments.
158+
159+
However, users can override this platform-level configured value by setting this value explicitly on the UI or on
160+
the SDK.
161+
162+
On the UI:
163+
164+
![CPU Limits](../../../images/override_cpu_limits.png)
165+
166+
On the SDK:
167+
168+
```python
169+
merlin.deploy(
170+
v,
171+
environment_name=some_name,
172+
resource_request=ResourceRequest(cpu_limit="2"),
173+
deployment_mode=some_deployment_mode,
174+
)
175+
```
176+
153177
## Liveness Probe
154178

155179
When deploying a model version, the model container will be built with a livenes probe by default. The liveness probe will periodically check that your model is still alive, and restart the pod automatically if it is deemed to be dead.

0 commit comments

Comments
 (0)