Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • 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
Hide categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Working with Node.js
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • PHP Behavior in Heroku
      • Working with PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Model Context Protocol
    • Vector Database
    • Heroku Inference
      • Inference Essentials
      • AI Models
      • Inference API
      • Quick Start Guides
    • Working with AI
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
  • 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
  • Integrating with Salesforce
  • Heroku Architecture
  • Compute (Dynos)
  • Dyno Behavior
  • Dyno Memory Behavior

Dyno Memory Behavior

Last updated March 28, 2025

Table of Contents

  • Memory Behavior
  • Additional Reading

Memory Behavior

The maximum amount of RAM available to your application depends on the dyno size you use. Using a dyno size that’s too small can cause constant memory swapping, which degrades application performance. Application metrics data, including memory usage, is available via the Metrics tab of the Heroku Dashboard. You can also measure memory with log-runtime-metrics. Memory leaks in your app can also cause usage problems. If you suspect a memory leak, try using memory profiling tools.

Swap isn’t available on all dynos in Private Spaces for example. Private-M dynos that vastly exceed their memory quota typically emit R15 errors without using swap space. Instead, the platform kills processes consuming large amounts of memory, but may not kill the dyno itself.

 

Using small amounts of swap space and infrequent memory swapping are usually not problematic. Even when your application hasn’t reached its memory limit, it’s common to see small amounts of memory being swapped to disk as the operating system manages memory and available disk cache.

The dyno manager restarts your dyno and logs an R15 error when the memory usage reaches the following limits for each dyno size.

For Cedar-Generation Apps

  • Eco, Basic or Standard-1X dyno: 1 GB, two times its quota.
  • Standard-2X dyno: 2 GB, two times its quota.
  • Performance-M dyno: 5 GB, two times its quota.
  • Performance-L dyno: 28 GB, two times its quota.
  • Performance-L-RAM dyno: 36 GB, 1.2 times its quota.
  • Performance-XL dyno: 74 GB, 1.2 times its quota.
  • Performance-2XL dyno: 151 GB, 1.2 times its quota.
  • Private-S or Shield-S dyno: its quota of 1 GB.
  • Private-M or Shield-M dyno: its quota of 2.5 GB.
  • Private-L or Shield-L dyno: its quota of 14 GB.
  • Private-L-RAM or Shield-L-RAM dyno: its quota of 30 GB.
  • Private-XL or Shield-XL dyno: its quota of 62 GB.
  • Private-2XL or shield-2XL dyno: its quota of 126 GB.

For Fir-Generation Apps

All dynos for Fir-generation apps get restarted when the memory usage reaches 100% of their quota.

Additional Reading

  • Dyno Scaling and Process Limits
  • Technical Specifications by Dyno Size
  • The Dyno Behavior category
  • Scaling Your Dyno Formation

Keep reading

  • Dyno Behavior

Feedback

Log in to submit feedback.

Rolling Deploys Dyno Restarts

Information & Support

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

Language Reference

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

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices