If the database continues to more perform I/O operations per second, then performance is brought back to the baseline PIOPS, which can heavily impact database performance. Architecture, vCPU, RAM and I/OĪll Heroku Postgres plans run on 64-bit architectures, ensuring both high performanceįor internal Postgres operations and interoperability with other features like Forks and Both read and write IOPS can be found in the Heroku Postgres Server metrics. 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ĭiscussion on Postgres caching can be found in Understanding Heroku Postgres Data Caching.Īll instances are backed by EBS-optimized instances where EBS disks with provisioned IOPsĪre 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Īll 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.Īll backup files that are taken using Heroku PGBackups are stored in an encrypted S3 bucket in the US region.So here’s my problem. I have a ton of data, and I need it to be dynamically available to run apps on my dashboard.

Heroku psequel