Last updated March 28, 2025
Memory BehaviorThe 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 AppsAll dynos for Fir-generation apps get restarted when the memory usage reaches 100% of their quota.
Additional ReadingRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4