# Space issues, recent

**URL:** https://meta.discourse.org/t/space-issues-recent/63948
**Category:** Feature
**Created:** [June 5, 2017, 11:59am UTC](https://meta.discourse.org/t/space-issues-recent/63948 "2017-06-05T11:59:07Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![JagWaugh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagwaugh/32/69335_2.png) [@JagWaugh](https://meta.discourse.org/u/JagWaugh)
#### Post date: [June 14, 2017, 7:08am UTC](https://meta.discourse.org/t/space-issues-recent/63948/7 "2017-06-14T07:08:40Z")

</div>

> [@Falco](#):
>
> I think this should be an warning in the app

That would be fine. We’re talking about the difference between Discourse **warning** you that your instance **might** stop working **soon** , and it just informing you that it has **already stopped working** (in the CLI) or failing to update via the GUI.

Warnings are less stressful than a broken installation (for the admin) and if they include a link to some basic triage then admins who don’t ignore the warnings may be able to resolve the issue themselves, rather than posting here on meta with “My instance is broken, what do I do?”

Some _rough_ idea of the RAM footprint (over time) of the instance would be great, down at the bottom of /admin where it shows space. The way I see it there are a lot of support topics which resolve down to RAM and disk space problems - warnings might reduce how often people need support.

---

_[View the full topic](https://meta.discourse.org/t/space-issues-recent/63948)._
