Skip to content

Commit e409216

Browse files
authored
Merge pull request #107934 from jonels-msft/compute-scaling
Can now adjust vCores via the UI
2 parents d23e7fc + a49b77d commit e409216

File tree

2 files changed

+17
-6
lines changed

2 files changed

+17
-6
lines changed

articles/postgresql/howto-hyperscale-alert-on-metric.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: jonels-msft
55
ms.author: jonels
66
ms.service: postgresql
77
ms.topic: conceptual
8-
ms.date: 2/18/2020
8+
ms.date: 3/16/2020
99
---
1010

1111
# Use the Azure portal to set up alerts on metrics for Azure Database for PostgreSQL - Hyperscale (Citus)
@@ -96,7 +96,7 @@ As the disk approaches its space limit, try these techniques to get more free sp
9696

9797
* Review data retention policy. Move older data to cold storage if feasible.
9898
* Consider [adding nodes](howto-hyperscale-scaling.md#add-worker-nodes) to the server group and rebalancing shards. Rebalancing distributes the data across more computers.
99-
* Consider [growing the capacity](howto-hyperscale-scaling.md#increase-vcores) of worker nodes. Each worker can have up to 2 TiB of storage. However adding nodes should be attempted before resizing nodes because adding nodes completes faster.
99+
* Consider [growing the capacity](howto-hyperscale-scaling.md#increase-or-decrease-vcores-on-nodes) of worker nodes. Each worker can have up to 2 TiB of storage. However adding nodes should be attempted before resizing nodes because adding nodes completes faster.
100100

101101
### CPU usage
102102

articles/postgresql/howto-hyperscale-scaling.md

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: jonels-msft
55
ms.author: jonels
66
ms.service: postgresql
77
ms.topic: conceptual
8-
ms.date: 12/17/2019
8+
ms.date: 3/16/2020
99
---
1010

1111
# Scale a Hyperscale (Citus) server group
@@ -45,13 +45,24 @@ The `rebalance_table_shards` function rebalances all tables in the
4545
argument. Thus you do not have to call the function for every distributed
4646
table, just call it on a representative table from each colocation group.
4747

48-
## Increase vCores
48+
## Increase or decrease vCores on nodes
4949

50-
In addition to adding new nodes, you can increase the capabilities of existing
51-
nodes. This feature is currently in preview — to request increased vCores for
50+
> [!NOTE]
51+
> This feature is currently in preview. To request a change in vCores for
5252
nodes in your server group, please [contact Azure
5353
support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
5454

55+
In addition to adding new nodes, you can increase the capabilities of existing
56+
nodes. Adjusting compute capacity up and down can be useful for performance
57+
experiments as well as short- or long-term changes to traffic demands.
58+
59+
To change the vCores for all worker nodes, adjust the **vCores** slider under
60+
**Configuration (per worker node)**. The coordinator node's vCores can be
61+
adjusted independently. Click the **Change configuration** link under
62+
**coordinator node**. A dialog will appear with sliders for the vCores and
63+
Storage capacity of the coordinator. Change the sliders as desired and select
64+
**OK**.
65+
5566
## Next steps
5667

5768
Learn more about server group [performance

0 commit comments

Comments
 (0)