Can anyone provide insight into the practical limits in terms of the number of files and maximum size of dyno created files (individually and in total) a Cedar based Heroku application can support.
Maximum storage of 1GB for hobby-dev and 10GB for hobby-basic plans. Maximum of 20 connections. No in-memory cache: The lack of an in-memory cache limits performance, because the data can't be accessed on low-latency storage.
Heroku has an “ephemeral” hard drive, this means that you can write files to disk, but those files will not persist after the application is restarted. By default Active Storage uses a :local storage option, which uses the local file system to store any uploaded files.
Build: Users are limited to 75 requests to Heroku Git repos per hour, per app, per user.
The Heroku filesystem is ephemeral - that means that any changes to the filesystem whilst the dyno is running only last until that dyno is shut down or restarted.
Contacted Heroku support.
They claim there are no hard limits on number of files or size of files stored on the ephmeral filesystem.
In practice, if a dyno uses up the available RAM and / or CPU resources managing the files, the dyno will be killed and restarted which will effectively destroy the files.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With