PostgreSQL on SAP BTP - Understanding service entitlements and metrics

[antoniojmnunes]

For deploying and using the service you need to have the proper entitlements in you Global Account regarding compute service plans (standard or premium) and storage service plans (storage or storage_ha).

☝️Each instance of PostgreSQL will consume always blocks of memory (compute) and blocks of storage.

In case of multi-AZ configurations, the double of memory blocks need to be considered and storage high availability variant is mandatory.

The consumption is metered daily for each instance and aggregated at sub-account and global account levels.
Both metrics usage are shown in the BTP Cockpit Usage Analytics view at global account and sub-account levels.

🔖 Understanding PostgreSQL service entitlements and metrics

The service has 4 service plans (that are measured by specific metrics). The service plans are compute and storage types. Compute plans are based on memory blocks and storage plans are based on storage blocks.

See below how the service plans are grouped and what are their metrics (by what they are measured):

For more detail and information, you can read Service Plans and Entitlements and Sizing sections in the service Help Portal documentation.

Different instance configurations and type support the desired size (memory), the instance types vary and depends on the hypescaler where you plan to deploy the service. 

🔖 How to check the resources allocated per instance (memory | storage)

You can check the instance configuration and the compute and storage allocated to each instance by accessing the parameters, via BTP Cockpit.

 For each instance you will be able to check what are the memory and storage resources allocated:

‌🔖‌ How many blocks of memory and storage do I need to for the above configuration example

Both above instances were created with multi-AZ, so we need to consider 'High Availability Storage' plan and for instance 1 we need to consider 'Premium' plan as the configuration of standard is only for 4GB or lower memory instances configurations. For instance 2 we consider 'Standard' plan.

Important: Because both instances are multi-AZ (multiple availability zones) we will need to consider the double of memory blocks. 

For each instance we will need to consider:

Instance 1:

• Service plan Premium with 8 GB of Memory and 200 GB of Storage High Availability
• Entitlements: 4 (4GB memory blocks) = 2 nodes x 8GB | 40 (5GB ha_storage blocks) = 200 GB

Instance 2:

• Service plan Standard with 4 GB of Memory and 100 GB of Storage High Availability
• Entitlements: 4 (2GB memory blocks) = 2 nodes x 4GB | 20 (5GB ha_storage blocks) = 100 GB

This means that in total you should have the below entitlements quota in your sub-account:

• Compute: 4 units of 4GB memory blocks + 4 units of 2GB memory blocks = 24 GB
• Storage : 40 units of 5GB ha_storage blocks + 20 x 5GB ha_storage blocks = 300 GB

For more detail and information, you can read the official documentation about Service Plans and Entitlements and Sizing in the service Help Portal documentation sections.

Check also other interesting blogs regarding PostgreSQL:

• PostgreSQL on SAP BTP - Are you looking for official blog posts? Blog INDEX

Thanks for your reading,

SAP BTP Backing Services – Product Management