Skip to content

Commit 5837197

Browse files
committed
Can now adjust vCores via the UI
1 parent 113ff17 commit 5837197

File tree

1 file changed

+11
-5
lines changed

1 file changed

+11
-5
lines changed

articles/postgresql/howto-hyperscale-scaling.md

Lines changed: 11 additions & 5 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,12 +45,18 @@ 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

5050
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
52-
nodes in your server group, please [contact Azure
53-
support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
51+
nodes. Adjusting compute capacity up and down can be useful for performance
52+
experiments as well as short- or long-term changes to traffic demands.
53+
54+
To change the vCores for all worker nodes, adjust the **vCores** slider under
55+
**Configuration (per worker node)**. The coordinator node's vCores can be
56+
adjusted independently. Click the **Change configuration** link under
57+
**coordinator node**. A dialog will appear with sliders for the vCores and
58+
Storage capacity of the coordinator. Change the sliders as desired and select
59+
**OK**.
5460

5561
## Next steps
5662

0 commit comments

Comments
 (0)