Skip to content

Commit ad5e729

Browse files
brhamilton529brhamilton529
committed
Merge branch 'frank/big-app-asa-e' of https://github.com/frankliu20/azure-docs-pr 
2 parents 8c2e986 + c4a019a commit ad5e729

File tree

4 files changed

+123
-14
lines changed

4 files changed

+123
-14
lines changed

‎articles/spring-apps/how-to-enterprise-large-cpu-memory-applications.md

Lines changed: 107 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,107 @@
1+
---
2+
title: How to deploy large CPU and memory applications in Azure Spring Apps in the Enterprise tier
3+
description: Learn how to deploy large CPU and memory applications in the Enterprise tier for Azure Spring Apps.
4+
author: karlerickson
5+
ms.author: haital
6+
ms.service: spring-apps
7+
ms.topic: how-to
8+
ms.date: 03/17/2023
9+
ms.custom: devx-track-java, devx-track-azurecli
10+
---
11+
12+
# Deploy large CPU and memory applications in Azure Spring Apps in the Enterprise tier
13+
14+
**This article applies to:** ❌ Basic/Standard tier ✔️ Enterprise tier
15+
16+
This article shows how to deploy large CPU and memory applications in Azure Spring Apps to support CPU intensive or memory intensive workloads. Support for large applications is currently available only in the Enterprise tier, which supports the CPU and memory combinations as shown in the following table.
17+
18+
| CPU (cores) | Memory (GB) |
19+
| ----------- | ----------- |
20+
| 4 | 16 |
21+
| 6 | 24 |
22+
| 8 | 32 |
23+
24+
## Prerequisites
25+
26+
- An Azure Spring Apps service instance.
27+
- [The Azure CLI](/cli/azure/install-azure-cli).
28+
29+
## Create a large CPU and memory application
30+
31+
You can use the Azure portal or the Azure CLI to create applications.
32+
33+
### [Azure portal](#tab/azure-portal)
34+
35+
Use the following steps to create a large CPU and memory application using the Azure portal.
36+
37+
1. Go to your Azure Spring Apps service instance.
38+
39+
1. In the navigation pane, select **Apps**, and then select **Create app**.
40+
41+
1. On the **Create App** page, provide a name for **App name** and select the desired **vCpu** and **Memory** values for your application.
42+
43+
1. Select **Create**.
44+
45+
:::image type="content" source="media/how-to-create-large-application/create-large-application.png" lightbox="media/how-to-create-large-application/create-large-application.png" alt-text="Screenshot of the Azure portal Create App page in Azure Spring Apps showing configuration settings for a new app.":::
46+
47+
### [Azure CLI](#tab/azure-cli)
48+
49+
The following command creates an application with the CPU set to eight core processors and memory set to 32 gigabytes.
50+
51+
```azurecli
52+
az spring app create \
53+
--resource-group <resource-group-name> \
54+
--service <Azure-Spring-Apps-service-instance-name> \
55+
--name <Spring-app-name> \
56+
--cpu 8 \
57+
--memory 32Gi
58+
```
59+
60+
---
61+
62+
## Scale up and down for large CPU and memory applications
63+
64+
To adjust your application's CPU and memory settings, you can use the Azure portal or Azure CLI commands.
65+
66+
### [Azure portal](#tab/azure-portal)
67+
68+
Use the following steps to scale up or down a large CPU and memory application.
69+
70+
1. On the overview page of your app, select **Scale up** in the navigation pane.
71+
72+
1. Select the preferred **vCpu** and **Memory** values.
73+
74+
:::image type="content" source="media/how-to-create-large-application/scale-large-application.png" lightbox="media/how-to-create-large-application/scale-large-application.png" alt-text="Screenshot of Azure portal Configuration page showing how to scale large app.":::
75+
76+
1. Select **Save**.
77+
78+
### [Azure CLI](#tab/azure-cli)
79+
80+
The following command scales up an app to have high CPU and memory values.
81+
82+
```azurecli
83+
az spring app scale \
84+
--resource-group <resource-group-name> \
85+
--service <Azure-Spring-Apps-service-instance-name> \
86+
--name <Spring-app-name> \
87+
--cpu 8 \
88+
--memory 32Gi
89+
```
90+
91+
The following command scales down an app to have low CPU and memory values.
92+
93+
```azurecli
94+
az spring app scale \
95+
--resource-group <resource-group-name> \
96+
--service <Azure-Spring-Apps-service-instance-name> \
97+
--name <Spring-app-name> \
98+
--cpu 1 \
99+
--memory 2Gi
100+
```
101+
102+
---
103+
104+
## Next steps
105+
106+
- [Build and deploy apps to Azure Spring Apps](/azure/spring-apps/quickstart-deploy-apps)
107+
- [Scale an application in Azure Spring Apps](/azure/spring-apps/how-to-scale-manual)

‎articles/spring-apps/media/how-to-enterprise-large-cpu-memory-applications/create-large-application.png

33.8 KB
Loading

‎articles/spring-apps/media/how-to-enterprise-large-cpu-memory-applications/scale-large-application.png

103 KB
Loading

‎articles/spring-apps/quotas.md

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -18,29 +18,31 @@ ms.custom: devx-track-java, event-tier1-build-2022
1818

1919
**This article applies to:** ✔️ Basic/Standard tier ✔️ Enterprise tier
2020

21-
All Azure services set default limits and quotas for resources and features. Azure Spring Apps offers two pricing tiers: Basic and Standard. We will detail limits for both tiers in this article.
21+
All Azure services set default limits and quotas for resources and features. Azure Spring Apps offers three pricing tiers: Basic, Standard, and Enterprise.
2222

2323
## Azure Spring Apps service tiers and limits
2424

25-
| Resource | Scope | Basic | Standard/Enterprise |
26-
|--------------------------------------|-----------------------------------------|--------------------|-------------------------------------------------|
27-
| vCPU | per app instance | 1 | 4 |
28-
| Memory | per app instance | 2 GB | 8 GB |
29-
| Azure Spring Apps service instances | per region per subscription | 10 | 10 |
30-
| Total app instances | per Azure Spring Apps service instance | 25 | 500 |
31-
| Custom Domains | per Azure Spring Apps service instance | 0 | 25 |
32-
| Persistent volumes | per Azure Spring Apps service instance | 1 GB/app x 10 apps | 50 GB/app x 10 apps |
33-
| Inbound Public Endpoints | per Azure Spring Apps service instance | 10 <sup>1</sup> | 10 <sup>1</sup> |
34-
| Outbound Public IPs | per Azure Spring Apps service instance | 1 <sup>2</sup> | 2 <sup>2</sup> <br> 1 if using VNet<sup>2</sup> |
35-
| User-assigned managed identities | per app instance | 20 | 20 |
25+
The following table defines limits for the pricing tiers in Azure Spring Apps.
26+
27+
| Resource | Scope | Basic | Standard | Enterprise |
28+
|--------------------------------------|-----------------------------------------|---------------------|--------------------------------------------------|--------------------------------------------------|
29+
| vCPU | per app instance | 1 | 4 | 8 |
30+
| Memory | per app instance | 2 GB | 8 GB | 32 GB |
31+
| Azure Spring Apps service instances | per region per subscription | 10 | 10 | 10 |
32+
| Total app instances | per Azure Spring Apps service instance | 25 | 500 | 500 |
33+
| Custom Domains | per Azure Spring Apps service instance | 0 | 25 | 25 |
34+
| Persistent volumes | per Azure Spring Apps service instance | 1 GB/app x 10 apps | 50 GB/app x 10 apps | 50 GB/app x 10 apps |
35+
| Inbound Public Endpoints | per Azure Spring Apps service instance | 10 <sup>1</sup> | 10 <sup>1</sup> | 10 <sup>1</sup> |
36+
| Outbound Public IPs | per Azure Spring Apps service instance | 1 <sup>2</sup> | 2 <sup>2</sup> <br> 1 if using VNet<sup>2</sup> | 2 <sup>2</sup> <br> 1 if using VNet<sup>2</sup> |
37+
| User-assigned managed identities | per app instance | 20 | 20 | 20 |
3638

3739
<sup>1</sup> You can increase this limit via support request to a maximum of 1 per app.
3840

3941
<sup>2</sup> You can increase this limit via support request to a maximum of 10.
4042

4143
> [!TIP]
42-
> Limits listed for Total app instances per service instance apply for apps and deployments in any state, including stopped state. Be sure to delete apps or deployments that aren't in use.
44+
> Limits listed for total app instances, per service instance, apply for apps and deployments in any state, including apps in a stopped state. Be sure to delete apps or deployments that are not being used.
4345
4446
## Next steps
4547

46-
Some default limits can be increased. If your setup requires an increase, [create a support request](../azure-portal/supportability/how-to-create-azure-support-request.md).
48+
Some default limits can be increased. For more information, see [create a support request](../azure-portal/supportability/how-to-create-azure-support-request.md).

0 commit comments

Comments
 (0)