You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The S3 bucket where we are storing the rendered animations is currently at 130 gigabytes, and growing by a couple hundred megabytes a minute.
It's not particularly necessary for us to store these long-term; the standard workflow is for users to download the videos locally rather than viewing them online, and the videos can always be reconstructed from the logs. Post-HOC, it would probably be worthwhile to set up an automatic purge of videos older than 30 days, and also construct a video download workflow that can regenerate deleted videos.
Additionally, the bucket where we store the logs is at 55 gigabytes; the log format itself is significantly more verbose than it needs to be, and could either be refactored or run through jsonc to mitigate this.
The text was updated successfully, but these errors were encountered:
The S3 bucket where we are storing the rendered animations is currently at 130 gigabytes, and growing by a couple hundred megabytes a minute.
It's not particularly necessary for us to store these long-term; the standard workflow is for users to download the videos locally rather than viewing them online, and the videos can always be reconstructed from the logs. Post-HOC, it would probably be worthwhile to set up an automatic purge of videos older than 30 days, and also construct a video download workflow that can regenerate deleted videos.
Additionally, the bucket where we store the logs is at 55 gigabytes; the log format itself is significantly more verbose than it needs to be, and could either be refactored or run through jsonc to mitigate this.
The text was updated successfully, but these errors were encountered: