# Disk usage spike during backup, Discourse crashed hard :-(

**URL:** https://meta.discourse.org/t/disk-usage-spike-during-backup-discourse-crashed-hard/157675
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [July 14, 2020, 6:50am UTC](https://meta.discourse.org/t/disk-usage-spike-during-backup-discourse-crashed-hard/157675 "2020-07-14T06:50:36Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [July 16, 2020, 6:08pm UTC](https://meta.discourse.org/t/disk-usage-spike-during-backup-discourse-crashed-hard/157675/19 "2020-07-16T18:08:02Z")

</div>

> [@pnoeric](#):
>
> so when images were living on Amazon S3, the bandwidth bill is really what killed me. Especially when I realized I could store all the images on the DO droplet and it would be included in the bandwidth/storage fees I already pay.

Sure, but that’s why you front S3 with a CDN. Don’t serve images directly from S3, that’s going to be ridiculously expensive 😱. You can front S3 with Cloudfront or even CloudFlare quite easily. The free tier of CloudFlare will achieve this.

And storing them locally is also pretty bad news, you’re going to need to scale up your VPS unnecessarily. Local SSD will be much costlier.

---

_[View the full topic](https://meta.discourse.org/t/disk-usage-spike-during-backup-discourse-crashed-hard/157675)._