Skip to content

Commit ee24906

Browse files
authored
Rename to web pubsub
1 parent 07e3070 commit ee24906

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

articles/azure-web-pubsub/howto-scale-manual-scale.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,32 +19,32 @@ The scale settings take a few minutes to apply. In rare cases, it may take aroun
1919
For information about the pricing and capacities of individual Web PubSub Service, see [Azure Web PubSub Service Pricing Details](https://azure.microsoft.com/pricing/details/web-pubsub/).
2020

2121
> [!NOTE]
22-
> Changing Web PubSub Service from **Free** tier to **Standard** or **Premium** tier or vice versa, the public service IP will be changed and it usually takes 30-60 minutes to propagate the change to DNS servers across the entire internet.
22+
> Changing Web PubSub Service from **Free** tier to **Standard** or **Premium** tier or vice versa, the public service IP will be changed and it usually takes 30-60 minutes to propagate the change to DNS servers across the entire internet. Chaning tiers between **Standard** and **Premium** will not change the public IP.
2323
> Your service might be unreachable before DNS gets updated. Generally it’s not recommended to change your pricing tier too often.
2424
2525

26-
## Scale Up on Azure portal
26+
## Scale up on Azure portal
2727

2828
1. In your browser, open the [Azure portal](https://portal.azure.com).
2929

3030
2. In your Web PubSub Service page, from the left menu, select **Scale Up**.
3131

3232
3. Click **Change** and select **Premium_P1** Tier in the pop out blade.
3333

34-
![Screenshot of scaling up on Portal.](./media/howto-scale-manual-scale/webpubsub-howto-scale-up.png)
34+
![Screenshot of scaling up on Portal.](./media/howto-scale-manual-scale/web-pubsub-howto-scale-up.png)
3535

3636
4. Select **Save**.
3737

3838

39-
## Scale Out on Azure portal
39+
## Scale out on Azure portal
4040

4141
1. In your browser, open the [Azure portal](https://portal.azure.com).
4242

4343
2. In your Web PubSub Service page, from the left menu, select **Scale Out**.
4444

4545
3. Choose the unit in the **Manual scale** sector.
4646

47-
![Screenshot of scaling out on Portal.](./media/howto-scale-manual-scale/webpubsub-howto-scale-out.png)
47+
![Screenshot of scaling out on Portal.](./media/howto-scale-manual-scale/web-pubsub-howto-scale-out.png)
4848

4949
4. Select **Save**.
5050

@@ -68,7 +68,7 @@ For detailed information, such as included messages and connections for each pri
6868
For a table of service limits, quotas, and constraints in each tier, see [Web PubSub Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-web-pubsub-limits).
6969

7070

71-
## Enhanced Large Instance Support with Premium_P2 SKU
71+
## Enhanced large instance support with Premium_P2 SKU
7272
The new Premium_P2 SKU (currently in Preview) is designed to facilitate extensive scalability for high-demand scenarios. This SKU allows scaling among 100, 200, 300, 400, 500, 600. 700, 800, 900, 1000 units for a single Web PubSub Service instance. This enhancement enables the handling of up to **one million** concurrent connections, catering to large-scale, real-time communication needs.
7373

7474
You can scale up the SKU to Premium_P2 using Azure portal or Azure CLI.

0 commit comments

Comments
 (0)