Skip to content

Commit b49dee2

Browse files
authored
Merge pull request #110462 from jonels-msft/hsc-conf
Updated data about RAM and IOPS
2 parents 156ab1b + b5b70df commit b49dee2

File tree

1 file changed

+48
-6
lines changed

1 file changed

+48
-6
lines changed

articles/postgresql/concepts-hyperscale-configuration-options.md

Lines changed: 48 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
2-
title: Performance options – Hyperscale (Citus) - Azure Database for PostgreSQL
2+
title: Configuration options – Hyperscale (Citus) - Azure Database for PostgreSQL
33
description: Options for a Hyperscale (Citus) server group, including node compute, storage, and regions.
44
author: jonels-msft
55
ms.author: jonels
66
ms.service: postgresql
77
ms.subservice: hyperscale-citus
88
ms.topic: conceptual
9-
ms.date: 2/18/2020
9+
ms.date: 4/6/2020
1010
---
1111

12-
# Azure Database for PostgreSQL – Hyperscale (Citus) performance options
12+
# Azure Database for PostgreSQL – Hyperscale (Citus) configuration options
1313

1414
## Compute and storage
1515

@@ -20,9 +20,7 @@ the logical CPU of the underlying hardware. The storage size for
2020
provisioning refers to the capacity available to the coordinator
2121
and worker nodes in your Hyperscale (Citus) server group. The storage
2222
includes database files, temporary files, transaction logs, and
23-
the Postgres server logs. The total amount of storage you provision
24-
also defines the I/O capacity available to each worker and coordinator
25-
node.
23+
the Postgres server logs.
2624

2725
| | Worker node | Coordinator node |
2826
|-----------------------|-----------------------|-----------------------|
@@ -32,6 +30,50 @@ node.
3230
| Storage type | General purpose (SSD) | General purpose (SSD) |
3331
| IOPS | Up to 3 IOPS/GiB | Up to 3 IOPS/GiB |
3432

33+
The total amount of RAM in a single Hyperscale (Citus) node is based on the
34+
selected number of vCores.
35+
36+
| vCores | One worker node, GiB RAM | Coordinator node, GiB RAM |
37+
|--------|--------------------------|---------------------------|
38+
| 4 | 32 | 16 |
39+
| 8 | 64 | 32 |
40+
| 16 | 128 | 64 |
41+
| 32 | 256 | 128 |
42+
| 64 | 432 | 256 |
43+
44+
The total amount of storage you provision also defines the I/O capacity
45+
available to each worker and coordinator node.
46+
47+
| Storage size, TiB | Maximum IOPS |
48+
|-------------------|--------------|
49+
| 0.5 | 1,536 |
50+
| 1 | 3,072 |
51+
| 2 | 6,148 |
52+
53+
For the entire Hyperscale (Citus) cluster, the aggregated IOPS work out to the
54+
following values:
55+
56+
| Worker nodes | 0.5 TiB, total IOPS | 1 TiB, total IOPS | 2 TiB, total IOPS |
57+
|--------------|---------------------|-------------------|-------------------|
58+
| 2 | 3,072 | 6,144 | 12,296 |
59+
| 3 | 4,608 | 9,216 | 18,444 |
60+
| 4 | 6,144 | 12,288 | 24,592 |
61+
| 5 | 7,680 | 15,360 | 30,740 |
62+
| 6 | 9,216 | 18,432 | 36,888 |
63+
| 7 | 10,752 | 21,504 | 43,036 |
64+
| 8 | 12,288 | 24,576 | 49,184 |
65+
| 9 | 13,824 | 27,648 | 55,332 |
66+
| 10 | 15,360 | 30,720 | 61,480 |
67+
| 11 | 16,896 | 33,792 | 67,628 |
68+
| 12 | 18,432 | 36,864 | 73,776 |
69+
| 13 | 19,968 | 39,936 | 79,924 |
70+
| 14 | 21,504 | 43,008 | 86,072 |
71+
| 15 | 23,040 | 46,080 | 92,220 |
72+
| 16 | 24,576 | 49,152 | 98,368 |
73+
| 17 | 26,112 | 52,224 | 104,516 |
74+
| 18 | 27,648 | 55,296 | 110,664 |
75+
| 19 | 29,184 | 58,368 | 116,812 |
76+
| 20 | 30,720 | 61,440 | 122,960 |
3577

3678
## Regions
3779
Hyperscale (Citus) server groups are available in the following Azure regions:

0 commit comments

Comments
 (0)