Skip Navigation
Show nav
Heroku Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
View categories

Categories

  • Heroku Architecture
    • Dynos (app containers)
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Command Line
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery
    • Continuous Integration
  • Language Support
    • Node.js
    • Ruby
      • Rails Support
      • Working with Bundler
    • Python
      • Working with Django
      • Background Jobs in Python
    • Java
      • Working with Maven
      • Java Database Operations
      • Working with the Play Framework
      • Working with Spring Boot
      • Java Advanced Topics
    • PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
    • Heroku Redis
    • Apache Kafka on Heroku
    • Other Data Stores
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
    • Compliance
  • Heroku Enterprise
    • Private Spaces
      • Infrastructure Networking
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
    • Single Sign-on (SSO)
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Databases & Data Management
  • Heroku Redis
  • Heroku Redis Technical Characterization

Heroku Redis Technical Characterization

English — 日本語に切り替える

Last updated 25 January 2021

Table of Contents

  • Performance characteristics
  • Multitenancy
  • Architecture, vCPU, RAM and I/O

All the information in this document is subject to change as Heroku adapts the service to better handle customer workloads.

The Heroku Redis Hobby, and Premium tier plans offer different performance characteristics based on their multitenancy, CPU, RAM and I/O architectures. This article provides a technical description of the implementation of these plans, and some of the performance characteristics of each.

Performance characteristics

The following table outlines our plans along with relevant specifications about the underlying hardware.

Plan vCPU RAM PIOPs Multitenant Connection Limit
hobby-dev 2 25 MB 200 yes 20
premium-0 2 50 MB 500 yes 40
premium-1 2 100 MB 500 yes 80
premium-2 2 250 MB 500 yes 200
premium-3 2 500 MB 500 yes 400
premium-4 2 750 MB 500 yes 700
premium-5 2 1 GB 500 yes 1000
premium-7 private-7 shield-7 2 7 GB 500 no 10000
premium-9 private-9 shield-9 4 10 GB 500 no 25000
premium-10 private-10 shield-10 8 25 GB 500 no 40000
premium-12 private-12 shield-12 16 50 GB 500 no 65000
premium-14 private-14 shield-14 32 100 GB 1000 no 65000

Premium, Private, and Shield plans are encrypted at rest by using AES-256, block-level storage encryption.

Multitenancy

Heroku Redis instances currently run on virtualized infrastructure provided by AWS EC2. Higher level Heroku Redis plans benefit from higher levels of resource isolation than lower level plans.

There are two main variants of deployment architectures on Heroku Redis: multi-tenant and single-tenant.

For multi-tenant plans, several LXC containers are created within a single large instance. Each LXC container holds a single Redis service and provides security and resource isolation within the instance.

Resource isolation and sharing on multi-tenant plans is imperfect and absolutely fair resource distribution between tenants cannot be guaranteed under this architecture.

For single-tenant plans, a customer’s Redis instance and related management software are the sole residents of resources on the instance, offering more predictable and less variable performance. However, virtualized infrastructure is still subject to some resource contention and minor performance variations are expected.

Architecture, vCPU, RAM and I/O

All Heroku Redis plans run on 64-bit architectures, ensuring best performance for Redis operations.

vCPU are the number of virtual processors on the underlying instance. Having a larger number of vCPUs provides better performance on the virtual server or instance.

All instances are backed by EBS optimized instances where EBS disks with provisioned IOPs (PIOPs) 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.

Keep reading

  • Heroku Redis

Feedback

Log in to submit feedback.

Understanding Heroku Redis Log Statements and Common Errors Securing Heroku Redis

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Podcasts
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing

Subscribe to our monthly newsletter

Your email address:

  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Heroku Podcasts
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Facebook
  • Instagram
  • Github
  • LinkedIn
  • YouTube
Heroku is acompany

 © Salesforce.com

  • heroku.com
  • Terms of Service
  • Privacy
  • Cookies