Heroku Postgres Production Tier Technical Characterization

Last updated 17 August 2018

Heroku Postgres plans offer different performance characteristics based on their CPU, RAM, and I/O architectures. This article provides a technical description of the implementation of these production plans, along with important performance characteristics for each plan.

Performance characteristics

The following table outlines Heroku Postgres production-tier plans, along with relevant specifications about the underlying hardware:

Run the pg:info command to check whether your Postgres database has an upgrade available:

$ heroku pg:info
=== HEROKU_POSTGRESQL_RED
Plan         Standard 4
Status       available
…
Improved Standard-4 Plans Available at the same price (2x RAM, 2x vCPU, 2x IOPS)
Learn More: https://blog.heroku.com/new-heroku-postgres-plans
Update Now: https://devcenter.heroku.com/articles/updating-heroku-postgres-databases

All Heroku Postgres plans aside from the hobby tier are single-tenant plans. A customer’s database and related management software are the sole residents of resources on the instance, offering more predictable performance. However, virtualized infrastructure is still subject to some resource contention, and minor performance variations are expected.

Burstable Performance

All Heroku Postgres plans come with a baseline level of performance, but standard-0, premium-0 and private-0 plans have the ability to burst past that baseline. Unlike a multi-tenancy model, burstable performance plans allows each database to run in isolation as a single-tenant instance. This means that when your database is provisioned, no other customer is running on the same server. In the event that your database bursts for an extended period of time, it is brought back to the original baseline level of performance. If a consistent level of performance is needed, a non-burstable Heroku Postgres plan provides fixed levels of performance.

The baseline level of performance is dictated by the plan type:

Each of these plans can burst past these load averages for a short amount of time. If the database has a sustained load over those amounts, however, it is brought back to the baseline. Load averages can be found in the Heroku Postgres Server metrics, which are part of your application’s logs.

Architecture, vCPU, RAM and I/O

All Heroku Postgres plans run on 64-bit architectures, ensuring both high performance for internal Postgres operations and interoperability with other features like Forks and Followers across all production-tier plans.

vCPU indicates the number of virtual processors on the underlying instance. A larger vCPU count provides higher performance on the virtual server or instance.

RAM is the approximate amount of memory used for data caching. An in-depth discussion on Postgres caching can be found in Understanding Heroku Postgres Data Caching.

All instances are backed by EBS-optimized instances where EBS disks with provisioned IOPs are attached. PIOPs are a measure of how many I/O operations the underlying disks can perform per second. The amount of IOPs provisioned for each plan determines its I/O throughput. On write-heavy applications, I/O can be a significant bottleneck, but on read-heavy ones, your hot dataset should fit in RAM and can therefore perform well with lower IOPs values.

Data encryption

All production plans (Standard, Premium, Private and Shield) are encrypted at rest with AES-256, block-level storage encryption. Keys are managed by Amazon, and individual volume keys are stable for the lifetime of the volume. You can find more detail about EBS encryption here. Heroku does not encrypt anything for you at the Postgres level, so if you wish to do this, you can use the PGCrypto extension for your own encryption.

All backup files that are taken using Heroku PGBackups are stored in an encrypted S3 bucket in the US region.

Technical characterization of databases created before January 17, 2018

Heroku Postgres plans provisioned before January 17, 2018, had the following performance characteristics: