Practical limits of Cedar's Ephemeral Filesystem on Heroku

Can anyone provide insight into the practical limits in terms of the number of 开发者_如何学Pythonfiles and maximum size of dyno created files (individually and in total) a Cedar based Heroku application can support.

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.

I've never run into a problem with any of my apps but they say slug size should be less than 200Mb, details here. You can't write any files to the filesystem except tmp which isn't guaranteed to be shared between your dynos so you have to write it out to Amazon S3 or such like.

Don't forget though, uploading a file will consume a dyno whilst the upload is taking place