Postgres Optimization & Performance Tuning

Services Overview

The EDB Postgres^® Optimization and Performance Tuning is designed to ensure the health and stability of your Postgres architecture. An EDB Consultant will work directly with your team to provide a deep dive audit of your existing Postgres database cluster(s). The EDB Consultant will review configurations, security, performance, and topology.

The service comes in three sizes, depending on the width of analysis needed by your team:

A Cluster is defined as a Primary Server and up to 3 additional Standby Servers. Each server in the cluster contains one Postgres Instance. An Instance is defined as a single running database service (PID) on a specific port.

Scope of Services

The engagement focuses on analyzing your environment and existing configuration parameters with respect to your current or planned use case. The EDB Consultant will analyze the following specific areas:

• Hardware and OS Configuration: Reviewing the underlying infrastructure supporting the database
• Database Architecture: Analyzing structural elements including Indices, Schemas, and Tablespaces per Cluster. Review of Backup Policy, replicas, and High Availability tooling to verify if expected RTO/RPO are met.
• Database Activity: Monitoring and reviewing the transactional activity of the database
• Configuration & Tuning: Reviewing Configuration Parameters, Concurrent Connections, and Query Timing
• Maintenance Strategy: Analyzing the current Vacuum Strategy to ensure optimal storage and performance
• Partitioning: Conducting a review of partitioning strategies

Deliverables

At the conclusion of the engagement, EDB will provide:

Comprehensive Architectural & Performance Optimization Report A detailed document providing a holistic view of your database health, containing:

• Scalability Assessment: An evaluation of your system's current readiness to support planned business operations, ensuring a robust structure for future growth.
• Configuration & Parameter Tuning: A specific "current vs. recommended" analysis of configuration parameters and settings, tailored to your specific use case to immediately improve performance.
• Architectural Optimization Roadmap: Actionable recommendations for structural improvements, covering indices, topology, schemas, and tablespaces to maximize efficiency. Recommendations on tooling for HA, Backup, and Connection Pooling.
• Maintenance & Storage Strategy: A review of your Vacuum Strategy and partitioning approach to ensure long-term database stability and optimal storage usage.
• Hardware & OS Alignment: Verification that your hardware and OS configurations are correctly aligned with your database activity and performance requirements.
• Report Review: A review of the report and findings with the customer via web conference

Roles & Responsibilities

EDB Project Manager:  Responsible for initial planning, task alignment, and project closeout.

EDB Senior Consultant: Technical Lead, responsible for workshop delivery, analysis, validation and documentation

Customer Team: Responsible for providing the main point of contact for the existing cluster requirements. Resources and Roles (or similar Technical Stakeholders) where input may be needed for the engagement include:

• System Architect
• Database Administrator
• Infrastructure Manager 
• Network Administrator
• Security Officer
• Application Owner

Assumptions

• A project kickoff will be conducted to review the service scope and confirm the schedule
• This service is delivered remotely unless otherwise agreed
• EDB Lasso Tool is required for the EDB Optimization and is available through the EDB support portal. 
• Customers will provide the names, title, email, phone number, and area of responsibility of those participating. One person will be designated as the main contact, and will be able to provide access to the people most knowledgeable about the topics to be discussed or examined. 
• Customers will make appropriate personnel available to assist EDB in the performance of the services as needed and requested by EDB in a timely manner so as not to disrupt the project schedule. 
• Customers will not provide Personal Data (as defined in applicable law). Customer agrees that it will work with EnterpriseDB to ensure that all such data is not provided.  
• Customer is responsible for providing all necessary internal design and project related documentation where EDB is required to analyze, and provide acc customer implemented systems.
• Customers will ensure timely access to all systems through screen sharing and experts including third parties as required. 
• Customers will assign the appropriate resources with the appropriate privileges for the task being planned for any screen sharing sessions as needed throughout the engagement.
• A Cluster is defined as a Primary Server and up to 3 additional Standby Servers. Each server in the cluster contains one Postgres Instance. An Instance is defined as a single running database service (PID) on a specific port.

Prerequisites

• Customer will identify target cluster(s) depending on the size of review purchased
• Customer will provide appropriate EDB Lasso Tool output for the proposed cluster(s)
• Customer will provide resource availability for workshop planning and a point of contact for coordination.
• Customer is responsible for providing all necessary internal design and project related documentation and requirements where EDB is required to analyze, operate, or modify customer implemented systems