# High memory use during assets precompilation

**URL:** <https://meta.discourse.org/t/high-memory-use-during-assets-precompilation/56526>\
**Category:** Development\
**Created:** [January 28, 2017, 6:57pm UTC](https://meta.discourse.org/t/high-memory-use-during-assets-precompilation/56526 "2017-01-28T18:57:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [January 30, 2017, 3:37pm UTC](https://meta.discourse.org/t/high-memory-use-during-assets-precompilation/56526/2 "2017-01-30T15:37:02Z")

</div>

@sgrif is painfully aware of this 🙂

The bad news, at the moment stuff is looking even worse if we upgrade to sprockets 4 (we are on 3)

The good news, some time this year we plan to move off [sprockets](https://github.com/rails/sprockets) altogether and make this a non-issue.

---

_[View the full topic](https://meta.discourse.org/t/high-memory-use-during-assets-precompilation/56526)._
