Home icon

Understanding how certain database parameters impact scaling in Amazon Aurora Serverless v2

Database Blog

The article discusses how certain database parameters impact scaling in Amazon Aurora Serverless v2 with PostgreSQL, focusing on how different configurations affect the database's ability to scale down to minimum Aurora Capacity Units (ACUs).

  • Key parameters examined include:
    • max_connections
    • max_locks_per_transaction
    • track_activity_query_size
  • Main observations:
  • Default parameters allow scaling down to 0.5 ACU
  • Nondefault parameter settings can prevent scaling to minimum ACU
  • Higher connection workloads require minimum ACU of 2 or higher
  • Recommendations:
  • Start with default parameters
  • Use minimum ACU of 2 for high-connection workloads
  • Consider using RDS Proxy to minimize connection overhead

    • The article emphasizes the importance of understanding how database parameters impact Aurora Serverless v2 scaling behavior to optimize performance and cost-effectiveness.

    Go to article

    The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.

    Related articles

    Nov 25
    2024
    Understanding how ACU minimum and maximum range impacts scaling in Amazon Aurora Serverless v2
    Nov 20
    2024
    Introducing scaling to 0 capacity with Amazon Aurora Serverless v2
    Nov 20
    2024
    Amazon Aurora Serverless v2 supports scaling to zero capacity
    Oct 23
    2024
    Evaluating the right fit for your Amazon Aurora workloads: provisioned or Serverless v2

    The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.