Performance issues after scaling up Azure Database for PostgreSQL - Flexible Server

Tigran Sardaryan 0 Reputation points
2024-11-11T21:13:35.8533333+00:00

We're running Azure Database for PostgreSQL - Flexible Server on General Purpose, D8ds_v5 (8 vCores, 32 GiB RAM) with 2Tb storage. After switching to D16ds_v5 (16 vCores, 64 GiB RAM) with 4Tb storage, the performance decreased significantly. All the server parameters are the same.

What could be the issue?

Azure Database for PostgreSQL
{count} votes

1 answer

Sort by: Most helpful
  1. NIKHILA NETHIKUNTA 3,505 Reputation points Microsoft Vendor
    2024-11-12T05:05:53.4+00:00

    @Tigran Sardaryan

    Thank you for the question and for using Microsoft Q&A platform.
    As per my understanding you are facing with Performance issues after scaling up Azure Database for PostgreSQL - Flexible Server with no change in server parameters.
    Here are some possible reasons for the performance decrease after upgrading to the D16ds_v5 instance:

    Resource Allocation and Configuration

    • CPU and Memory Utilization: Verify that the additional vCores and RAM are being effectively utilized. Applications or queries might need adjustments to take full advantage of these increased resources.
    • Connection Pooling: Check if your connection pooling settings are optimized. Excessive short-lived connections can lead to high CPU usage.

    I/O Performance

    • Disk I/O: With the change in storage size, I/O performance characteristics may have shifted. Ensure that I/O operations aren't becoming a bottleneck.
    • Storage Configuration: Confirm that the storage configuration (such as IOPS and throughput) is suitable for your workload requirements.

    Query Performance

    • Query Plans: The query execution plans might have been altered due to the new hardware configuration. Review and optimize query plans as needed.
    • Indexing: Ensure that indexes remain effective with the new setup. Hardware changes can sometimes affect indexing performance.

    Auto vacuum and Maintenance

    • Auto vacuum Settings: Verify that autovacuum settings are still appropriate. Inefficient autovacuum settings can cause performance degradation.
    • Maintenance Tasks: Make sure that regular maintenance tasks, like vacuuming and analyzing, are running as expected.

    Additionally, you can utilize the Troubleshooting Guides in the Azure portal to diagnose specific issues like high CPU usage, memory constraints, or I/O performance bottlenecks. These guides provide tailored charts, guidelines, and recommendations to address your specific performance challenges.

    For more information, please refer to the below links:
    https://techcommunity.microsoft.com/blog/adforpostgresql/empower-your-troubleshooting-with-azure-database-for-postgresql---flexible-serve/3794263
    https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-high-cpu-utilization?tabs=postgres-13
    https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-high-io-utilization
    https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-autovacuum-tuning
    https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-identify-slow-queries
    https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-optimize-query-stats-collection

    Hope this helps. Do let us know if you have any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.