Skip to content

Commit 6111cec

Browse files
Address warnings.
1 parent c0e1b81 commit 6111cec

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/app-service/configure-custom-container.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to configure a custom container in Azure App Service. Thi
44
author: msangapu-msft
55
ms.author: msangapu
66
ms.topic: how-to
7-
ms.date: 003/06/2025
7+
ms.date: 03/06/2025
88
ms.custom: devx-track-azurepowershell, devx-track-azurecli, linux-related-content
99
zone_pivot_groups: app-service-containers-windows-linux
1010
---
@@ -329,6 +329,8 @@ Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WE
329329

330330
The value is defined in MB and must be less and equal to the total physical memory of the host. For example, in an App Service plan with 8 GB of RAM, the cumulative total of `WEBSITE_MEMORY_LIMIT_MB` for all the apps must not exceed 8 GB. For more information on how much memory is available, see the **Premium v3 service plan** section of [App Service pricing](https://azure.microsoft.com/pricing/details/app-service/windows/).
331331

332+
## Customize the number of compute cores
333+
332334
By default, a Windows container runs with all available cores for your chosen pricing tier. You might want to reduce the number of cores that your staging slot uses. To reduce the number of cores used by a container, set the `WEBSITE_CPU_CORES_LIMIT` app setting to the preferred number of cores. You can set it by using the [Cloud Shell](https://shell.azure.com). In Bash:
333335

334336
```azurecli-interactive

0 commit comments

Comments
 (0)