Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting our team. We will be in touch shortly.Close

Performance and resource allocation

This page covers topics related to measuring and configuring the performance of PostgreSQL


Performance testing

For performance testing and benchmarking charms, we recommend using the Charmed Sysbench operator. This is a tool for benchmarking database applications that includes monitoring and CPU/RAM/IO performance measurement.

Resource allocation

Charmed PostgreSQL resource allocation can be controlled via the charm’s profile config option. There are two profiles: production and testing.

Value Description Details
production
(default)
Maximum performance 25% of the available memory for shared_buffers and the remain as cache memory (defaults mimic legacy charm behaviour).
The max_connections=max(4 * os.cpu_count(), 100).
Use pgbouncer if max_connections are not enough (reasoning).
testing Minimal resource usage PostgreSQL 14 defaults.

Note: Pre-deployed application profile change is planned but currently is NOT supported.

You can set the profile during deployment using the --config flag. For example:

juju deploy postgresql --config profile=testing

You can change the profile using the juju config action. For example:

juju config postgresql profile=production

For a list of all of this charm’s config options, see the Configuration tab.

Juju constraints

The Juju --constraints flag sets RAM and CPU limits for Juju units:

juju deploy postgresql --constraints cores=8 mem=16G

Juju constraints can be set together with the charm’s profile:

juju deploy postgresql --constraints cores=8 mem=16G --config profile=testing

Last updated 3 months ago. Help improve this document in the forum.